Dear Clint,
maybe you misunderstood a little, or I didn't write it explicitly. We use
OpenStack for providing a VPS service, yes. But the VPS users do not get access
to OpenStack directly, but instead, they use our Customer Portal which does the
orchestration. The whole point is to make the serv
Hi ,
You can use alot of tools to create virtual machines in openstack.
The quick answers are:
1. Terraform
2. Ansible
Currently I am using a python library developed at CERN-IT called AITOOLS
that uses the openstack api to create virtual machines and bind them to
puppet and forem
Thanks Tomas, I did understand you, I just didn't make my point perfectly.
The point is that OpenStack has two very different missions today, and
that is causing my frustration and I have let that go for now. There
is a hosting mission, where we try to keep computing pets alive, and a
cloud missio
This came up in IRC discussion the other day, but we didn't dig into it
much given we were all (2 of us) exhausted talking about rebuild.
But we have had several bugs over the years where people expect the root
disk to change to a newly supplied image during rebuild even if the
instance is vol
Why not supporting this use case?
Same reason as before: A user might wish to keep its IP addresses.
The use cannot do the following to bypass the limitation:
1) stop instance
2) detach root volume
3) delete root volume
4) create new volume
5) attach as root
6) boot instance
Last time I tried, o
On Fri, Oct 6, 2017 at 1:32 PM, Mathieu Gagné wrote:
> Why not supporting this use case?
>
> Same reason as before: A user might wish to keep its IP addresses.
>
> The use cannot do the following to bypass the limitation:
> 1) stop instance
> 2) detach root volume
> 3) delete root volume
> 4) crea
+1
I am also personally frustrated by the same thing clint is,
It seems that somewhere along the line we lost the direction of cloud vs
VPS, and somewhere it was sold (or not sold) that openstack is good for
both (when it really isn't imho),
http://cloudscaling.com/blog/cloud-computing/the-h
I've been chasing something weird I was seeing in devstack when creating
hundreds of instances in a single request where at some limit, things
blow up in an unexpected way during scheduling and all instances were
put into ERROR state. Given the environment I was running in, this
shouldn't have
On 10/6/2017 1:30 PM, Joshua Harlow wrote:
+1
I am also personally frustrated by the same thing clint is,
It seems that somewhere along the line we lost the direction of cloud vs
VPS, and somewhere it was sold (or not sold) that openstack is good for
both (when it really isn't imho),
http:/
On 10/6/2017 1:10 PM, Mathieu Gagné wrote:
I don't think there ever was a technical limitation to add support for it.
See the review comments with the -1 votes on the patches I linked
originally.
There are valid technical reasons for the -1s on those, including on
this one from Paul Murray
10 matches
Mail list logo
