thanks Aaron ;)
2014-07-22 5:22 GMT+07:00 Aaron Rosen :
> Hi Nhan,
>
> Instead of trying to use the cisco device to do the NAT'ing for you it
> would probably be easiest to use the openstack neutron l3-agent to provide
> this functionality for you.
>
> Aaron
>
>
> On Wed, Jul 16, 2014 at 8:55 AM
I have seen this behavior when overcloud stack is not ready. Go to the
Undercloud node and run "heat stack-list" to know the status of overcloud
stack. If it is stuck at IN PROGRESS or ended in ERROR status, such behavior is
observed.
From: 严超 [mailto:yanchao...@gmail.com]
Sent: Monday, July 2
Everything is OK except nova command in overcloud can't be used. Maybe
keystone is configured wrongly ?
(undercloud)chaoya@ironic001:~/tripleo/tripleo-incubator$ heat
resource-list overcloud
+-+---+-+--+
|
Hi,
I know that this could be an "off-topic" question, but I'm having
problem changing the default gateway on a VM. In particular, I have 3 VM
(let's say VM1, VM2 and VM3).
I would like to have the following scenario:
VM1 <--> VM2 <--> VM3
that means that the VM1 and VM3 have to contact VM2
Hi Shri,
The Object Storage API change is just to add a header called
'X-Storage-Policy: ' where name is set in the swift configuration
files by the cloud provider.
See http://docs.openstack.org/developer/swift/overview_policies.html
We'll add it to the API docs next, no version change needed for
This is confusing. So does this mean semantic versioning applies to
the API's and not the Swift product versions? If so how are the
product versions decided? And given a product version, how does one
know about what API version is in use? The /info endpoint does not
mention the API version.
I had
Hi all,
I testing upgrade from Havana to Icehouse. This is changing a number
of networking related things so not sure which is my problem. My goal
is to maintain my current production state jumbo frames network.
In Havana production I'm using openvswitch plugin, but not
LibvirtHybridOVSBridgeDr
Semantic versioning is bigger than just API changes. In fact, since we
separately version the API, we can actually be quite explicit about what's in a
particular release. In general, we do semantic versioning in Swift for a few
reasons, but the main one is that it's been requested and confirmed
> Hope this helps clear things up.
This does. Thanks for the detailed explanation.
-Shri
>
> --John
>
>
>
>
>
>
> On Jul 22, 2014, at 10:05 AM, Shrinand Javadekar
> wrote:
>
>> This is confusing. So does this mean semantic versioning applies to
>> the API's and not the Swift product versions?
To answer my own question...
the qbr devices are created by nova-network not neutron so their
configuration needs to go on nova.conf:
[default]/network_device_mtu=9000
so yay two place to enter the same value for the same purpose
On Tue, Jul 22, 2014 at 1:24 PM, Jonathan Proulx wrote:
> Hi all
Hi Thiago.
I think I may have figured out some more pieces to the puzzle regarding the
inconsistent results I mentioned earlier. For the most part I've been using
the dashboard to create/launch/terminate images. There is a directory on
each compute node /var/lib/nova/instances/ which seems to cont
Ubuntu 12.04 Cloud Archive support of OpenStack releases Folsom,
Grizzly and Havana will end on July 31, 2014 as outlined in the Ubuntu Cloud
Archive support schedule:
https://wiki.ubuntu.com/ServerTeam/CloudArchive/
If you using the Ubuntu Cloud Archive for OpenStack support on Ubuntu 12.04,
Hi,
I got some problems about python-six in nova-xxx.log like "Could not
load 'file': (six 1.4.1 (/usr/local/lib/python2.7/dist-packages),
Requirement.parse('six<1.4.1'))" , but when i install six=1.3.0, they shows
"Requirement.parse('six=>1.4.1')"
anyone know what's wrong? it seems h
13 matches
Mail list logo
