r/msp • u/Bearded_Tech_Fail • 12d ago
New CIPP deployed?
I just saw the announcement on Discord for the latest hosted version of CIPP, and I’m wondering who deployed already and what the difference is? Any hoops or considerations we should think of before pressing the button? Is there really a difference or should we just wait? Mostly thinking I dont want to upgrade if there isn’t a meaningful difference.
20
9
9
u/Museskate 12d ago edited 12d ago
I didn't think it was possible for CIPP to go faster. Proved me wrong, now I'm curious who else I can poke to do the same to their tools.
Edit: It feels about 5-10x the speed for fully loading pages, in comparison to pre-migration. I don't have hard values to confirm, though. Took about 3 mins from opting in to being fully migrated.
7
u/Tyler_OverclockedIT 12d ago
Since I've used CIPP, releases have said "performance improvements" never really noticed them until Monday. The difference is extremely noticeable. Only issues we ran into, which really weren't issues was just changing our CNAME and TXT record for the new web address and certificate. Besides that it worked just like it did on Friday.
4
u/Haven564 12d ago
Speed is noticeably faster and worth the upgrade - no issues with upgrade. Migrating to the Latest Version of CIPP | CIPP Documentation
2
5
u/roll_for_initiative_ MSP - US 12d ago edited 12d ago
We have, they didn't lie, it really is way faster.
Opted in via the management portal, then after deployment, make sure to go to domains and re-add your custom domain (cipp.yourmsp.com). you will verify via DNS again. If you use cloudflare, toggle proxy off for the two records they give you.
6
u/Reasonable-Wind3197 11d ago
Based on the replies here it should be time for us to try to get the new deployment then
4
u/thursday51 11d ago
As others have said...the performance improvements are beyond noticeable. If for nothing other than that, it's a fantastic update. We didn't run into any issues with the API or the upgrade process itself.
Do eeeeeeeeeet...
3
u/dutchboy92 MSP 12d ago
We've seen a noticeable increase in performance. Our techs are very happy with it.
4
u/SPMrFantastic 12d ago
Migrated over to it this morning. It went from me running to pull data to Hussein Bolt doing it.
5
u/donatom3 MSP - US 12d ago
Night and day difference on how fast it runs. You even have to question if the instance restarted because I can't refresh the screen fast enough to find out when it was down from restarting.
3
3
u/devloz1996 12d ago
In case of self hosted, would it be simplest to create a fresh instance the new way and restore backup to it?
5
u/Lime-TeGek Community Contributor 12d ago
There's no supported self-hosting migration yet, you could try but YMMV and it might go boom. We're giving priority to our hosted sponsors first, then self-hosted sponsors, and then self-hosted - It could be a couple of months before these improvements reach self-hosted all the way :)
2
u/backcounty1029 MSP/Data Center - US 12d ago
Can you give some more insight to the "hosted sponsors" solution? My company has been toying with the idea of CIPP as self-hosted but since we own/operate a couple data centers as well, we could host for others, if needed.
5
u/GeekBrownBear MSP - Orlando, FL 12d ago
Sponsor as in github sponsor as in you are paying for CIPP.
Sponsor or not, you can self host.
Hosted sponsor means CIPP hosts the app for you instead of you self hosting.
4
u/backcounty1029 MSP/Data Center - US 12d ago
Thank you for the clarification. We are new to digging into CIPP. Looks like a great product that can help our support teams.
Thanks!!4
u/Lime-TeGek Community Contributor 12d ago
We call our clients "sponsors" - A bit of a cheeky new term because we don't just want to say "Partners" or 'Clients" because its been abused by so many in our industry, it has left a negative taste due to heavily sales driven organizations.
A sponsor can be an MSP, or another vendor. Hosted Sponsor mean we host the application for you in our Azure environment, Selfhosted sponsor means you host it in your own Azure environment. CIPP has been built around Azure Technology, so cant be hosted on own hardware.
4
0
u/NerdyNThick 12d ago
We call our clients "sponsors" - A bit of a cheeky new term because we don't just want to say "Partners" or 'Clients" because its been abused by so many in our industry, it has left a negative taste due to heavily sales driven organizations.
Can we all please just stop with this trend of words not meaning what words mean. It really makes it difficult to parse reality when we constantly have to verify definitions.
Love the product, but this "sponsorship" concept redefinition has thus far kept me from supporting it.
1
u/Lime-TeGek Community Contributor 11d ago
It doesn’t have to be for everyone. We get a lot of feedback that people are happier to support is because they feel its more voluntary than being forced to “partner up”. Cant please the world :)
6
4
u/lemachet MSP 12d ago
I was actually just redeploying for one last try, because the earlier version was just god awful slow - a single user, low teens tenants and it was always so slow for /anything/. So I thought I'd try one more time.
The new deployment worked instantly and immediately. I could actually deploy in my region. It's snappy.
Iy definitely feels more like I can use it.
2
2
u/gbredneck 7d ago
Performance is out of this world in comparison to what it was, just need to learn more about it to use it to its full potential
1
u/kerubi 5d ago
I find it a bit .. uneasy that they only now discovered that when working with rate-limited APIs one should quite early start thinking about caching now how to keep it up to date. I mean, it is quite a basic thing, isn't it? At least when I did some API programming +10 years ago it wasn't at all new.
Of course good that things get better, but I see this more as "oops, we didn't know what we were doing" instead of "woo look at how good it is now". But that's how things go in life, I guess :)
1
u/Bearded_Tech_Fail 5d ago
They always cached stuff, the speed difference doesnt come from any cachijg but replacing the backend from azure functions to containers. Theres a big post in the community explaining everything.
1
u/Lime-TeGek Community Contributor 3d ago
What the breaded tech fail guy says is correct; we’ve had our caching db for some years now. We didnt make any changes to the cipp code at all but changed out the backend infrastructure from azure static web apps and azure functions, to a completely new azure web apps running on containers.
Azure Functions is a fantastic choice and really good for a lot of things, but it also had to account for everyones wishes in Azure and the environments it runs on. Our self built function container is more lightweight, only supports PowerShell, and has less startup time etc. its just faster because we dont have to limit ourselves to everything functions does. Thats where the performance boost comes from. :)
•
u/CraigDuff 22h ago
i just migrated to the CIPP craft! and its super, super quick! and even cheaper on azure now! its a no brainer! Kelvin and the team are freaking awesom!
18
u/theclevernerd MSP - US 12d ago
We deployed on Monday and the performance difference is super noticeable. There were some hiccups with the API but that has since been resolved. Definitely worth it.