is still the 'guest network' model. This blueprint, for
> which some code is already available on gerrit, just addresses the authZ
> work necessary for ensuring multiple tenants can share the same network
> object.
Understood. Thanks for the clear explanation.
Tomoe
>
>
Hi Dan,
On Thu, Jul 19, 2012 at 11:58 PM, Dan Wendlandt wrote:
>
>
> On Tue, Jul 17, 2012 at 7:39 PM, Tomoe Sugihara wrote:
>>
>> Hi Salvatore,
>>
>> I have a few questions regarding your proposal mostly related to L3
>> services.
>> I've
Hi Salvatore,
I have a few questions regarding your proposal mostly related to L3 services.
I've read in another thread that L3 services are out of Quantum's scope for
Folsom, but I'd like to know how this public network model would work
with those services.
1. What are the assumptions for publi
Hi Doude,
I was dealing with another issue caused by this NULL 'host', and Dan told
me that has been fixed:
https://github.com/openstack/nova/commit/43f2492175d11a3f8ea4198e65b2a6a6b38cbbb6
I haven't verified, though. Good luck.
Best,
Tomoe
On Thu, Mar 1, 2012 at 10:11 PM, Doude wrote:
> Hi,
Hey Anthony,
On Wed, Feb 22, 2012 at 3:11 AM, Anthony Young
wrote:
> Hey Tomoe,
>
>>
>> Great idea! Both of those sound good to me. Would you like to implement
>> this?:)
>
>
> Lol, perhaps, but at the very least this warrants a blueprint:
> https://blueprints.launchpad.net/nova/+spec/nova-creat
c "while ! ping -c1 -w1
>> $FLOATING_IP; do sleep 1; done"; then
>> +#echo "Couldn't ping volume-backed server with floating ip"
>> +#exit 1
>> +#fi
>>
>> # Make sure our volume-backed instance launched
>> -ssh -o StrictHostKeyChecking
Hi,
Is anyone working on getting floating ip work with melange?
Currently pool operation (from nova-manage) and
allocate/deallocate/associate/disassocaite (in FloatingIP mix-in for
network manager) are closely coupled with nova DB. I'd be happy to
work on that or work together if someone is alread
a delete $INSTANCE_NAME
# De-allocate the floating ip
-nova floating-ip-delete $FLOATING_IP
+#nova floating-ip-delete $FLOATING_IP
# Delete secgroup
nova secgroup-delete $SECGROUP
--
Hope this helps.
Cheers,
Tomoe
On Sat, Feb 11, 2012 at 10:31 PM, Tomoe Sugihara wrote
Hi Anthony,
Thanks for following it up.
On Sat, Feb 11, 2012 at 2:58 PM, Anthony Young
wrote:
> On Fri, Feb 10, 2012 at 8:51 PM, Tomoe Sugihara wrote:
>>
>> Hi folks,
>>
>> Could someone tell me what is the right way to do boot-from-volume?
>> Especially, how t
Hi folks,
Could someone tell me what is the right way to do boot-from-volume?
Especially, how to create boot-from-volume capable image and volume?
My understanding is that, since openstack API requires imageRef, we
need to pass in both image and volume ids.
I thought that create_image in EC2 API
spec. Ie, it'll need to go under
>> nova/api/openstack/compute/contrib in the tree, not directly in
>> compute/servers.py.
>>
>> - Chris
>>
>> On Jan 17, 2012, at 9:21 PM, Vishvananda Ishaya wrote:
>>
>>> You can propose code without an ap
Ishaya wrote:
>
>> You can propose code without an approved blueprint. Are you sure there isn't
>> already a server action for stop/start?
>>
>> Vish
>>
>> On Jan 17, 2012, at 7:46 PM, Tomoe Sugihara wrote:
>>
>>> Hi,
>>>
>>> I
Hi,
I have put up a blueprint
(https://blueprints.launchpad.net/nova/+spec/start-stop-methods-support-in-os-servers-api)
for supporting start/stop compute api, which should work well for
boot-from-volume from OpenStack API, and
I'm happy to contribute code for Essex release.
Could someone tell me
13 matches
Mail list logo
