Solved

Image creation V3 vs V2


Badge +3
Hi All,
If I use the V3 API (Prims Central) I cannot specify a container destination. This was possible with V2. Am I doing something wrong?

Thanks in advance.
icon

Best answer by Jon 17 April 2018, 08:53

Hey @tudamp - sorry no one responded to this, I'll jump in here. In short, you're not doing anything wrong. Note that in AOS 5.6, which came out today, we've GA'd the v3 API's, and have made significant improvements across the board. This however is not one of them. When provisioning VM's in through the v3 API, they'll land in the SelfServiceContainer as the default bucket. The whole point here is that this level of API abstraction separates the underlying infrastructure from the rest of the world.

You do have a good point though, and we do see that as a use case, so we'll work on improving this mid/long term as we add even more functionality into v3

View original

1 reply

Userlevel 7
Badge +30
Hey @tudamp - sorry no one responded to this, I'll jump in here. In short, you're not doing anything wrong. Note that in AOS 5.6, which came out today, we've GA'd the v3 API's, and have made significant improvements across the board. This however is not one of them. When provisioning VM's in through the v3 API, they'll land in the SelfServiceContainer as the default bucket. The whole point here is that this level of API abstraction separates the underlying infrastructure from the rest of the world.

You do have a good point though, and we do see that as a use case, so we'll work on improving this mid/long term as we add even more functionality into v3

Reply