This message was deleted.
# citrix-vad
s
This message was deleted.
n
We're probably reaching the threshold of having to increase headcount to accommodate the amount of general administration overhead there is with Citrix, so if we can do more with less by leveraging a new tool, may be win/win.
b
I don't have input personally on layering.. but timely enough, there is a CUGC/Liquidware FlexApp webinar next week, 6th Dec, 1p EST (-5GMT) https://mycugc.org/events/#/list
๐Ÿ‘ 1
s
is the current process automated (packer/MDT/ansible)? Or just manually updating the Master MCS VMs when updates come out?
โคด๏ธ 1
j
Automation probably better route. App Layering has improved composition engine.
b
I guess I assumed low hanging fruit like not stick driving everything was already done. Never assume Jon.
n
We have MDT in place to compile the gold images in an automated fashion, so that has at least been done.
s
coming from an environment that was very heavy applayering a couple year ago, i would never go back. 100% automation i the way to go. What don't you like about the current process or what takes the longest?
j
App Layering has had some nice updates and getting better.
b
Hello, Layering PM here. ๐Ÿ™‚ Of course I am biased, but there is investment needed in any solution, leveraging automation or not. App Layering will remove much of the heavy lifting (by removing the repetitive changes needed to maintain like components across all the images), without requiring the up front and ongoing investment and maintenance in development of end-to-end automation. That said, I do understand the motivation to automate, since once you get to that point it will in theory be much lower TCO. What if you could have both though? We are actively working on a full API for App Layering... in this scenario you could move faster across all fronts. Removing repetition, and automating some/all of the overhead to doing it. On top of this, depending when you were last using App Layering, we have made many improvements to streamline the packaging and publishing process too, such as offloading compositing as @Jarian Gibson mentioned.
๐Ÿ™Œ 1
b
@Daniel Lazar What's the timeframe on the API release? Is it in preview now?
b
No still early development. Likely we will begin to have releasable capabilities further into next year. There is an API specification we can share to get feedback on the planned capabilities.
Please let me know (you or anyone) if you want to be added to list to get the spec.