jclouds-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Everett Toews <everett.to...@RACKSPACE.COM>
Subject Re: problem with network ordering in OpenStack
Date Tue, 19 Nov 2013 15:01:15 GMT
In CreateServerOptions networks is handled as a Set so no order is guaranteed.

Is there a particular reason you need networks to be ordered when the request is sent to OpenStack?

Everett


On Nov 19, 2013, at 8:10 AM, Limor Bortman wrote:

Hi and thanks for the response:
1) this is how I create the CreateServerOptions :  CreateServerOptions Options = CreateServerOptions.Builder.keyPairName(addKeyPair(machine))
                .securityGroupNames(addSecurityGroups(machine))
                .networks(addNetworks(machine)).availabilityZone(addZone(machine));
When addNetworks return LinkedList

2) serverApiForZone.create(machineName, cloudNodeImage.getUuid(), computeOfferingId, Options);

3)I am using a Grizzly node

Thanks




On Tue, Nov 19, 2013 at 3:59 PM, Everett Toews <everett.toews@rackspace.com<mailto:everett.toews@rackspace.com>>
wrote:
Can you share a snippet of code with us?

Specifically, it would be good to see how you create your List of networks, how you create
your CreateServerOptions, and how you call ServerApi.create.

Also, what version of jclouds and what version of OpenStack are you using?

Thanks,
Everett


On Nov 19, 2013, at 3:51 AM, Limor Bortman wrote:

>
> Hello all
> I am trying to create machine on OpenStack with specific network ordering, but i find
out that sometimes jclouds change the order before sending it to the node .
>
> I am using the function ServerApi.create and set the order I want in the CreateServerOptions
>
> does anybody saw this problem?
> Thanks Limor
>




--
בורטמן לימור
"אם הייתי צנועה הייתי מושלמת"

Mime
View raw message