Re: [openstack-dev] [monasca][swift][storyboard] migration experience

2017-04-21 Thread Jeremy Stanley
On 2017-04-21 09:00:47 + (+), witold.be...@est.fujitsu.com wrote: > one thing which hasn't been migrated are the blueprints. We have > noticed this after the migration. Storyboard team has said they > had not planned on migrating blueprints because most of the > projects use the specs serve

Re: [openstack-dev] [monasca][swift][storyboard] migration experience

2017-04-21 Thread witold.be...@est.fujitsu.com
> >2) Are you missing anything from the migration? How do you manage > >security bugs that are embargoed? Hi John, one thing which hasn't been migrated are the blueprints. We have noticed this after the migration. Storyboard team has said they had not planned on migrating blueprints because mo

Re: [openstack-dev] [monasca][swift][storyboard] migration experience

2017-04-20 Thread Hochmuth, Roland M
Hi John, Comments in-line below. I'm hoping that someone else will add more details. On 4/17/17, 2:50 PM, "John Dickinson" wrote: >Moasca-teers > >As the migration away from Launchpad and to Storyboard moves forward, >the Swift team has been considering making the move. Monasca has >already

[openstack-dev] [monasca][swift][storyboard] migration experience

2017-04-17 Thread John Dickinson
Moasca-teers As the migration away from Launchpad and to Storyboard moves forward, the Swift team has been considering making the move. Monasca has already made the move, so I'd love to hear your thoughts on that process. 1) How did you do the change? All at once or gradually? If you did it over