Making blueprint upgrades easier - feature proposal

[Alex Heneveld <al...@cloudsoftcorp.com>]

Hi All-

I've been working with a few others on how we can simplify the process 
writing new versions of blueprints and applying them to existing 
deployments.

* Imagine being able to do *cat blueprint.bom | * **br catalog add 
--upgrade --restart* to have deployments pick up a new version of a 
blueprint you're working *on (and an editor in the UI)** * Move towards 
a pure infrastructure as code ideal where all changes are done by 
redeploying blueprints (as opposed to changing config programmatically)

Let us know what you think -- whether general, you like the idea, or a 
super-specific question on some subtle implication of a network config 
change.

The doc is attached as PDF and at [1].

Best
Alex

[1] 
https://docs.google.com/document/d/1Lm47Kx-cXPLe8BO34-qrL3ZMPosuUHJILYVQUswEH6Y

Re: Making blueprint upgrades easier - feature proposal

[Alex Heneveld <al...@cloudsoftcorp.com>]

(Seems the mailing list has stripped my PDF.  Attaching again in case 
that works but you'll probably have to use the link.)


On 29/03/2017 14:44, Alex Heneveld wrote:
>
> Hi All-
>
> I've been working with a few others on how we can simplify the process 
> writing new versions of blueprints and applying them to existing 
> deployments.
>
> * Imagine being able to do *cat blueprint.bom | * **br catalog add 
> --upgrade --restart* to have deployments pick up a new version of a 
> blueprint you're working *on (and an editor in the UI)** * Move 
> towards a pure infrastructure as code ideal where all changes are done 
> by redeploying blueprints (as opposed to changing config programmatically)
>
> Let us know what you think -- whether general, you like the idea, or a 
> super-specific question on some subtle implication of a network config 
> change.
>
> The doc is attached as PDF and at [1].
>
> Best
> Alex
>
> [1] 
> https://docs.google.com/document/d/1Lm47Kx-cXPLe8BO34-qrL3ZMPosuUHJILYVQUswEH6Y
>