Re: [Openstack] Fwd: Documentation for openstack-java-sdk
Surely Luis can help you, I've used openstack-java-sdk in one of my
projects, and this is the example Luis gave to me
private static final File TEST_FILE = new File(pom.xml);
private static final String KEYSTONE_AUTH_URL =
https://region-a.geo-1.identity.hpcloudsvc.com:35357/v2.0;;
private static final String KEYSTONE_USERNAME = ;
private static final String KEYSTONE_PASSWORD = ;
/**
* @param args
*/
public static void main(String[] args) throws Exception {
KeystoneClient keystone = new KeystoneClient(KEYSTONE_AUTH_URL);
//access with unscoped token
Access access = keystone.execute(Authenticate.withPasswordCredentials(
KEYSTONE_USERNAME, KEYSTONE_PASSWORD));
//use the token in the following requests
keystone.setToken(access.getToken().getId());
Tenants tenants = keystone.execute(new ListTenants());
//try to exchange token using the first tenant
if(tenants.getList().size() 0) {
access =
keystone.execute(Authenticate.withToken(access.getToken().getId()).withTenantId(tenants.getList().get(0).getId()));
SwiftClient swiftClient =
newSwiftClient(KeystoneUtils.findEndpointURL(access.getServiceCatalog(),
object-store, null, public), access.getToken().getId());
//swiftClient.execute(new DeleteContainer(navidad2));
swiftClient.execute(new CreateContainer(navidad2));
System.out.println(swiftClient.execute(new ListContainers()));
ObjectForUpload upload = new ObjectForUpload();
upload.setContainer(navidad2);
upload.setName(example2);
upload.setInputStream(new FileInputStream(TEST_FILE));
swiftClient.execute(new UploadObject(upload));
System.out.println(swiftClient.execute(new ListObjects(navidad2,
new HashMapString,
String() {{
put(path, );
}})).get(0).getContentType());
}
}
On Thu, Jul 11, 2013 at 11:31 AM, Endre Karlson endre.karl...@gmail.comwrote:
I think Luis can answer that?
-- Videresendt melding --
Fra: Jobin Raju George jobin...@gmail.com
Dato: 11. juli 2013 14:38
Emne: [Openstack] Documentation for openstack-java-sdk
Til: openstack lista openstack@lists.launchpad.net
Kopi:
I am trying to query ceilometer using
openstack-java-sdkhttps://github.com/woorea/openstack-java-sdkfor meters of
VM's running on KVM. I am able to get the CPU meters via curl
on the command line but unfortunately I don't find good documentation for
the SDK's for ceilometer.
I have seen this example
programhttps://github.com/woorea/openstack-java-sdk/blob/master/openstack-examples/src/main/java/com/woorea/openstack/examples/metering/v2/TestAll.java
but
most of it is commented(probably because it is deprecated).
Where can I find good documentation/examples or java programs/snippets?
--
Thanks and regards,
Jobin Raju George
Third Year, Information Technology
College of Engineering Pune
Alternate e-mail: georgejr10...@coep.ac.in
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
--
*guilherme* \n
\t *maluf*
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Fwd: Documentation for openstack-java-sdk
I know nothing about ceilometer.
I think the best thing is to checkout the classes on github and make a lot
of tests. Probably to functioning of objects and methods are the same in
ceilometer.
CHeckout the methods and try to workout with it.
:)
Good luck!
On Thu, Jul 11, 2013 at 11:59 AM, Jobin Raju George jobin...@gmail.comwrote:
Thanks a log, Gui! This helps but would be more useful if you could point
me to some *ceilometer-specific *guides/examples.
On Thu, Jul 11, 2013 at 8:25 PM, Gui Maluf guimal...@gmail.com wrote:
Surely Luis can help you, I've used openstack-java-sdk in one of my
projects, and this is the example Luis gave to me
private static final File TEST_FILE = new File(pom.xml);
private static final String KEYSTONE_AUTH_URL =
https://region-a.geo-1.identity.hpcloudsvc.com:35357/v2.0;;
private static final String KEYSTONE_USERNAME = ;
private static final String KEYSTONE_PASSWORD = ;
/**
* @param args
*/
public static void main(String[] args) throws Exception {
KeystoneClient keystone = new KeystoneClient(KEYSTONE_AUTH_URL);
//access with unscoped token
Access access = keystone.execute(Authenticate.withPasswordCredentials(
KEYSTONE_USERNAME, KEYSTONE_PASSWORD));
//use the token in the following requests
keystone.setToken(access.getToken().getId());
Tenants tenants = keystone.execute(new ListTenants());
//try to exchange token using the first tenant
if(tenants.getList().size() 0) {
access =
keystone.execute(Authenticate.withToken(access.getToken().getId()).withTenantId(tenants.getList().get(0).getId()));
SwiftClient swiftClient =
newSwiftClient(KeystoneUtils.findEndpointURL(access.getServiceCatalog(),
object-store, null, public), access.getToken().getId());
//swiftClient.execute(new DeleteContainer(navidad2));
swiftClient.execute(new CreateContainer(navidad2));
System.out.println(swiftClient.execute(new ListContainers()));
ObjectForUpload upload = new ObjectForUpload();
upload.setContainer(navidad2);
upload.setName(example2);
upload.setInputStream(new FileInputStream(TEST_FILE));
swiftClient.execute(new UploadObject(upload));
System.out.println(swiftClient.execute(new ListObjects(navidad2, new
HashMapString,
String() {{
put(path, );
}})).get(0).getContentType());
}
}
On Thu, Jul 11, 2013 at 11:31 AM, Endre Karlson
endre.karl...@gmail.comwrote:
I think Luis can answer that?
-- Videresendt melding --
Fra: Jobin Raju George jobin...@gmail.com
Dato: 11. juli 2013 14:38
Emne: [Openstack] Documentation for openstack-java-sdk
Til: openstack lista openstack@lists.launchpad.net
Kopi:
I am trying to query ceilometer using
openstack-java-sdkhttps://github.com/woorea/openstack-java-sdkfor meters
of VM's running on KVM. I am able to get the CPU meters via curl
on the command line but unfortunately I don't find good documentation for
the SDK's for ceilometer.
I have seen this example
programhttps://github.com/woorea/openstack-java-sdk/blob/master/openstack-examples/src/main/java/com/woorea/openstack/examples/metering/v2/TestAll.java
but
most of it is commented(probably because it is deprecated).
Where can I find good documentation/examples or java programs/snippets?
--
Thanks and regards,
Jobin Raju George
Third Year, Information Technology
College of Engineering Pune
Alternate e-mail: georgejr10...@coep.ac.in
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
--
*guilherme* \n
\t *maluf*
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
--
Thanks and regards,
Jobin Raju George
Third Year, Information Technology
College of Engineering Pune
Alternate e-mail: georgejr10...@coep.ac.in
--
*guilherme* \n
\t *maluf*
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Openstack Metadata Service
From what I understood, without the retrieval of the metadata from the server, the keys are not downloaded to the VM, is this correct? Yes. This is correct. AFAIK in Essex, the metadata service was pointed out through iptables. So there was a rule that DNAT the metadata service to the CC machine. I had this metadata problem too, but I couldn't find out a proper solution. My guess is that this problem is related to the Gateway/Router in Folsom+Quantum installation. Or maybe in the metadata_host in the nova.conf file. I hope someone could clarify this things for us. regards. On Mon, Mar 18, 2013 at 7:32 AM, Bruno Parreira bsen...@gmail.com wrote: Hi, We have deployed OpenStack using the guide provided at the OpenStack webpage: Host A : controller node Host B : network node Host C : compute node Everything went fine during the installation process, but when we try to instantiate a VM, the logs show that the VMs are unable to connect to the metadata service (169.254.169.254). We've tried this with the Ubuntu image and the Cirros image, but the result is the same. From what I understood, without the retrieval of the metadata from the server, the keys are not downloaded to the VM, is this correct? Because we can ping the IP address assigned to the VM from the network node, and if we assign a floating IP to the VM, the public IP also responds to ping replys. But we are unable to ssh into the VMs, with the error: Read from socket failed: Connection reset by peer If we try to telnet into the public IP this is the result: controller@controller:~$ telnet x.x.x.x 22 Trying x.x.x.x... Connected to x.x.x.x. Escape character is '^]'. SSH-2.0-OpenSSH_5.9p1 Debian-5ubuntu1 Protocol mismatch. Connection closed by foreign host. Questions: In which node is the metadata service supposed to be running (compute, network or controller)? Should the IP address 169.254.169.254 be reachable outside the VM? Is there an alternative to the metadata service? Kind regards, Bruno Parreira ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- *guilherme* \n \t *maluf* ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [Swift] Administration Interfaces/Tools for Swift
Nice things guys! I think for the monitoring purpose swift is well served. There is many tools that make the work. But seems that there is a lack of a admin interface, right? What I've found on SwiftStack looks pretty, but unfortunately their tool is paid, and I couldnt get how much they want for that. I'll keep searching for something, if I find something I'll come back here! Thank you guys! On Tue, Jan 29, 2013 at 4:48 PM, Florian Hines florian.hi...@gmail.comwrote: Theres actually 2 diamond plugin's for swift now. I added the one we use internally at Rackspace a week or two ago https://github.com/BrightcoveOS/Diamond/wiki/collectors-OpenstackSwiftReconCollector. In addition to these and Zenoss theres also been nagios and collectd plugins floating around. At least in our deployments Swifts built in statsd metrics become a bit overwhelming (both in volume of metrics and what metrics are actually being reported). This is probably just a side effect of the size of our clusters. We ended up sticking with our original statsd/metric setup (a combo of some proxy middleware, and translating a bunch of Swift's syslog lines to statsd events). -- Florian Hines | @pandemicsyn http://about.me/pandemicsyn On Tuesday, January 29, 2013 at 12:16 PM, Dieter Plaetinck wrote: On Tue, 29 Jan 2013 15:24:31 -0200 Gui Maluf guimal...@gmail.com wrote: Hi guys, I'm searching for a Swift Interface that integrates Administration and maybe monitoring. I've checked SwiftStack http://swiftstack.com/ and Gladinet http://gladinet.blogspot.com.br/2012/06/basic-layer-on-top-of-openstack-swift.html , but both are not opensource and require money to be used. There is something available that could ease admins tasks on swift? Thanks in advance! for monitoring, you can use https://github.com/Dieterbe/graph-explorer (graphite dashboard) which displays data (amongst others) from https://github.com/BrightcoveOS/Diamond (which has a swift plugin) as well as from the built in statsd support into swift i'm the author of graph-explorer and the diamond openstack swift plugin (i wrote these things cause i also couldn't find anything existing) i actually plan to write a blog post about these things soonish. Dieter ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- *guilherme* \n \t *maluf* ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] [Swift] Administration Interfaces/Tools for Swift
Hi guys, I'm searching for a Swift Interface that integrates Administration and maybe monitoring. I've checked SwiftStack http://swiftstack.com/ and Gladinethttp://gladinet.blogspot.com.br/2012/06/basic-layer-on-top-of-openstack-swift.html, but both are not opensource and require money to be used. There is something available that could ease admins tasks on swift? Thanks in advance! -- *guilherme* \n \t *maluf* ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Question about Disk Setup of Nova Compute Node
Hey Sean, Did you found which is the best set up for your RAID? I'm facing the same situation here. I've 11 dell r710 servers, with 4x3TB disk each, and I'm wondering if worth it using a RAID5 or JBOD for some server that will run a compute-network-volume node. Did you got any solution? Thanks in advance On Sat, Jan 12, 2013 at 7:21 PM, Razique Mahroua razique.mahr...@gmail.comwrote: Sorry, the first sentence is wrong : Hi, actually, even for a raid 10 you would end up with 3TB usable (more around 2800 GB) In both cases you end up with 2 TB :) Regards, *Razique Mahroua** - **Nuage Co* razique.mahr...@gmail.com Tel : +33 9 72 37 94 15 Le 12 janv. 2013 à 22:19, Razique Mahroua razique.mahr...@gmail.com a écrit : Hi, actually, even for a raid 10 you would end up with 3TB usable (more around 2800 GB). You could even go for either a RAID6 or RAID10 actually, since you have 4TB you would end up with 2TB in both cases Performance wise RAID10 is in most cases faster when it comes to reading speed, sometimes slower when it comes to writing speed, it all depends on you controller. You would bench both RAIDs and pick the faster one :) *Razique Mahroua** - **Nuage Co* razique.mahr...@gmail.com Tel : +33 9 72 37 94 15 NUAGECO-LOGO-Fblan_petit.jpg Le 11 janv. 2013 à 23:23, Sean Bigdatafun sean.bigdata...@gmail.com a écrit : Razique, Let's think of the following scenario, we use Nova to build an EC2-kind of compute cluster. For EC2, they offer M1.Small = 1 vCPU + 1.7GB Mem + 160GB Disk M1.Medium = 2vCPU + 3.75GB Mem + 410GB Disk M1.Large = 4vCPU + 7.5GB Mem + 850GB Disk M1.ExtraLarge = 8.vCPU + 15GB Mem + 1.7TB Dsik ... This means that they at least have 1.7TB disk space on a physical server (presumably 2 x 1TB disk). What RAID option would we use in designing our cluster? For our Nova compute nodes, -- Do we have a JBOD configuration of 2 disks? -- do we have a RAID 0 of 2 disks? -- or do we use more enterprise like RAID 5? Thanks and hopefully this starts some discussion in this direction. Thanks, Sean On Fri, Jan 11, 2013 at 12:46 AM, Razique Mahroua razique.mahr...@gmail.com wrote: Hi Sean, I may be wrong, but I think there is not any best RAID strategy when it comes to the disk for the nodes or a normal one. All RAID type have their pros and cons. It'a all about security over performance against total space that would end up usable. What RAID controller is that? Regards, *Razique Mahroua** - **Nuage Co* razique.mahr...@gmail.com Tel : +33 9 72 37 94 15 NUAGECO-LOGO-Fblan_petit.jpg Le 11 janv. 2013 à 08:36, Sean Bigdatafun sean.bigdata...@gmail.com a écrit : When I have a set of rack servers that is 1TB * 4 disks in each of it as Nova Compute Node, what is the best RAID (or JBOD) strategy OpenStack community recommend? Basically I'd like to know what a normal disk setup a compute node should be using. Thanks, Sean ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- --Sean ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- *guilherme* \n \t *maluf* NUAGECO-LOGO-Fblan_petit.jpg___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] OpenStack Java SDK
frans, you can always use devstack for a fast local OS deploy. Antonio I've interest in openstack-java-sdk, the only difference is that I'm using scala, instead of Java. I'm quite new at this and having a lot a difficulty trying to make my code connect with Keystone. I hope you can get your answer! Att. On Wed, Jan 9, 2013 at 10:07 PM, Frans Thamura fr...@meruvian.org wrote: hi Antonio talking Java SDK. is there OpenSTack on the Net, that we can use, to test this SDK? I love to invest in this tools, esp we are working with Java education program here F On Thu, Jan 10, 2013 at 6:51 AM, Antonio Manuel Muñiz Martín amu...@klicap.es wrote: Hello all. We are working with OpenStack Java SDK [1] since some months ago. Now we need to use it with Folsom. After a look on master branch we decided to keep us in the stable branch, because the project has no release policy, no tags... Said this, we've done some changes in stable Essex branch to adapt it to Folsom, basically adding some fields to resources required for a correct JSON mapping. If some of you think this changes are interesting we can send a pull request to the owner (Luis, I think you are in this list, I would like to get your opinion). Cheers, Antonio. [1] https://github.com/woorea/openstack-java-sdk/tree/stable/essex -- Antonio Manuel Muñiz Martín Software Developer at klicap - ingeniería del puzle work phone + 34 954 894 322 www.klicap.es | blog.klicap.es ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- *guilherme* \n \t *maluf* ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Developing with Scala/Java on OpenStack Swift
Luis, thanks for your quick reply! Seems I'm missing something very
important, because I can't use all this classes/types(Access, Authenticate,
Tenants, KeystoneUtils, ObjectForUpload,etc).
I've installed the os-java-sdk in this way:
$ git clone
$ mvn compile package
$ find . -name '*.jar' -exec cp {} sbt_lib_dir/. \;
$ sbt console
import org.openstack._
What am I doing wrong? What am I missing?
Is there a proper way to install the os-java-sdk?
Thank you very much!
With lots of regards.
On Thu, Jan 3, 2013 at 4:00 AM, Luis Gervaso l...@woorea.es wrote:
Hi Gui!
I just upgraded the code to work properly with latest Jersey release
Below the swift example code (just tested and working with HPCloud)
Hope it helps you :)
private static final File TEST_FILE = new File(pom.xml);
private static final String KEYSTONE_AUTH_URL =
https://region-a.geo-1.identity.hpcloudsvc.com:35357/v2.0;;
private static final String KEYSTONE_USERNAME = ;
private static final String KEYSTONE_PASSWORD = ;
/**
* @param args
*/
public static void main(String[] args) throws Exception {
KeystoneClient keystone = new KeystoneClient(KEYSTONE_AUTH_URL);
//access with unscoped token
Access access = keystone.execute(Authenticate.withPasswordCredentials(
KEYSTONE_USERNAME, KEYSTONE_PASSWORD));
//use the token in the following requests
keystone.setToken(access.getToken().getId());
Tenants tenants = keystone.execute(new ListTenants());
//try to exchange token using the first tenant
if(tenants.getList().size() 0) {
access =
keystone.execute(Authenticate.withToken(access.getToken().getId()).withTenantId(tenants.getList().get(0).getId()));
SwiftClient swiftClient =
newSwiftClient(KeystoneUtils.findEndpointURL(access.getServiceCatalog(),
object-store, null, public), access.getToken().getId());
//swiftClient.execute(new DeleteContainer(navidad2));
swiftClient.execute(new CreateContainer(navidad2));
System.out.println(swiftClient.execute(new ListContainers()));
ObjectForUpload upload = new ObjectForUpload();
upload.setContainer(navidad2);
upload.setName(example2);
upload.setInputStream(new FileInputStream(TEST_FILE));
swiftClient.execute(new UploadObject(upload));
System.out.println(swiftClient.execute(new ListObjects(navidad2, new
HashMapString,
String() {{
put(path, );
}})).get(0).getContentType());
}
}
On Wed, Jan 2, 2013 at 8:01 PM, Gui Maluf guimal...@gmail.com wrote:
Hey guys,
I'm trying to extend a software
projecthttps://github.com/VirtualCloudDrive/CloudDriveto talk with Swift.
This project was developed on Scala, and my issue is: how should I access
Swift resource? Should I use
openstack-java-sdkhttps://github.com/woorea/openstack-java-sdk/,
jclouds http://www.jclouds.org/documentation/quickstart/openstack/ or
develop my own library to access the REST API?
I've tried to use openstack-java-sdk but I wasn't able to import the
libraries exposed at examples.
I'm really confuse about that and I'll appreciate any help, hint, advice!
Thanks in advance.!
--
*guilherme* \n
\t *maluf*
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
--
---
Luis Alberto Gervaso Martin
Woorea Solutions, S.L
CEO CTO
mobile: (+34) 627983344
luis@ luis.gerv...@gmail.comwoorea.es
--
*guilherme* \n
\t *maluf*
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
[Openstack] Developing with Scala/Java on OpenStack Swift
Hey guys, I'm trying to extend a software projecthttps://github.com/VirtualCloudDrive/CloudDriveto talk with Swift. This project was developed on Scala, and my issue is: how should I access Swift resource? Should I use openstack-java-sdkhttps://github.com/woorea/openstack-java-sdk/, jclouds http://www.jclouds.org/documentation/quickstart/openstack/ or develop my own library to access the REST API? I've tried to use openstack-java-sdk but I wasn't able to import the libraries exposed at examples. I'm really confuse about that and I'll appreciate any help, hint, advice! Thanks in advance.! -- *guilherme* \n \t *maluf* ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Instances can't reach metadata server in network HA mode
Vish, if you could help.
I realized that all internal route of my vms point to cloudcontroller. if I
change the default route to node address everything works perfectly.
How can I make the node IP the default route?
Thanks for all help!
On Wed, Dec 19, 2012 at 2:34 PM, Gui Maluf guimal...@gmail.com wrote:
Yes, it's in multi_host=true. In nova.conf and in the database multi_host
is set to True. 10.5.5.32 isn't the gateway, instead is the private network.
LoL
Out of nothing my instances can now reach metadata. But when I login and
ping www.google.com VM can resolv name but there is no answer back, all
packets are lost. And I've attached a floating IP for two vms, on
different node, and they dont even ping back in the same node.
This is so confused! I'll do some tcpdump to check what is happening!
On Wed, Dec 19, 2012 at 2:05 PM, Vishvananda Ishaya vishvana...@gmail.com
wrote:
Are you sure your network has multi_host = True? It seems like it isn't,
since the gateway listed by the guest is 10.5.5.32
In multi_host mode each node should be getting an ip from the fixed range
and the guest should be using that as the gateway.
Vish
On Wed, Dec 19, 2012 at 1:13 PM, Vishvananda Ishaya
vishvana...@gmail.com wrote:
There should be a redirect in iptables from
169.254.169.254:80http://169.254.169.254/to $my_ip:8775 (where
nova-api-metadata is running)
So:
a) can you
curl $my_ip:8775 (should 404)
CloudController and Nodes awnser in the same way:
1.0
2007-01-19
2007-03-01
2007-08-29
2007-10-10
2007-12-15
2008-02-01
2008-09-01
2009-04-04
b) if you do
sudo iptables -t nat -L -n v
do you see the forward rule? Is it getting hit properly?
there is the correct rule, but they never got hit
controller
0 0 DNAT tcp -- * * 0.0.0.0/0
169.254.169.254 tcp dpt:80 to:200.131.6.250:8775
nodes
0 0 DNAT tcp -- * * 0.0.0.0/0
169.254.169.254 tcp dpt:80 to:200.131.6.248:8775
0 0 DNAT tcp -- * * 0.0.0.0/0
169.254.169.254 tcp dpt:80 to:200.131.6.249:8775
Thanks for appearing Vish! I was wishing your help!
Vish
On Dec 19, 2012, at 6:39 AM, Gui Maluf guimal...@gmail.com wrote:
My set up is a
nova-network-hahttp://docs.openstack.org/trunk/openstack-compute/admin/content/existing-ha-networking-options.html,
so each of my nodes run a nova-{api-metadata,network,compute,volume}, my
controller runs all of this plus the rest of things it should run.
Each of my nodes are the gateway for it's own instances. They all have
the same net config, ip_forwarding.
The main issue is that I can't telnet the nodes on port 80 that should
redirect to metadatas server. metadata IP is set correctly to eth0, but 80
port is not open.
My doubt is, should I create a endpoint for each node api-metadata
service? should I install apache on nodes?
I really don't know what to do anymore. This only happen on nodes, on
cloudcontroller all instance run smoothly. they get the floatip, metadata
service, etc.
Thanks in advance!
I will put the max of info I can here.
root@oxala:~# nova-manage service
list
Binary Host Zone
Status State Updated_At
nova-compute xangonova
enabled:-) 2012-12-18 20:34:21
nova-network xangonova
enabled:-) 2012-12-18 20:34:20
nova-compute oxossi nova
enabled:-) 2012-12-18 20:34:15
nova-network oxossi nova
enabled:-) 2012-12-18 20:34:20
nova-volume oxossi nova
enabled:-) 2012-12-18 20:34:18
nova-volume xangonova
enabled:-) 2012-12-18 20:34:19
nova-consoleauth oxalanova
enabled:-) 2012-12-18 20:34:24
nova-scheduler oxalanova
enabled:-) 2012-12-18 20:34:25
nova-certoxalanova
enabled:-) 2012-12-18 20:34:25
nova-volume oxalanova
enabled:-) 2012-12-18 20:34:25
nova-network oxalanova
enabled:-) 2012-12-18 20:34:17
nova-compute oxalanova
enabled:-) 2012-12-18 20:34:10
*controller nova.conf*
#NETWORK
--allow_same_net_traffic=true
--network_manager=nova.network.manager.FlatDHCPManager
--firewall_driver=nova.virt.libvirt.firewall.IptablesFirewallDriver
--public_interface=eth0
--flat_interface=eth1
--flat_network_bridge=br100
--fixed_range=10.5.5.32/27
--network_size=32
--flat_network_dhcp_start=10.5.5.33
--my_ip=200.131.6.250
--multi_host=True
#--enabled_apis=ec2,osapi_compute,osapi_volume,metadata
--dhcpbridge_flagfile=/etc/nova/nova.conf
--dhcpbridge=/usr/bin/nova-dhcpbridge
Re: [Openstack] Instances can't reach metadata server in network HA mode
Found out!
I'd a /etc/dnsmasq-nova.conf file defining the default route as my
controller node! now everything is working perfectly! :D
On Thu, Dec 20, 2012 at 11:07 AM, Gui Maluf guimal...@gmail.com wrote:
Vish, if you could help.
I realized that all internal route of my vms point to cloudcontroller. if
I change the default route to node address everything works perfectly.
How can I make the node IP the default route?
Thanks for all help!
On Wed, Dec 19, 2012 at 2:34 PM, Gui Maluf guimal...@gmail.com wrote:
Yes, it's in multi_host=true. In nova.conf and in the database multi_host
is set to True. 10.5.5.32 isn't the gateway, instead is the private network.
LoL
Out of nothing my instances can now reach metadata. But when I login and
ping www.google.com VM can resolv name but there is no answer back, all
packets are lost. And I've attached a floating IP for two vms, on
different node, and they dont even ping back in the same node.
This is so confused! I'll do some tcpdump to check what is happening!
On Wed, Dec 19, 2012 at 2:05 PM, Vishvananda Ishaya
vishvana...@gmail.com wrote:
Are you sure your network has multi_host = True? It seems like it isn't,
since the gateway listed by the guest is 10.5.5.32
In multi_host mode each node should be getting an ip from the fixed
range and the guest should be using that as the gateway.
Vish
On Wed, Dec 19, 2012 at 1:13 PM, Vishvananda Ishaya
vishvana...@gmail.com wrote:
There should be a redirect in iptables from
169.254.169.254:80http://169.254.169.254/to $my_ip:8775 (where
nova-api-metadata is running)
So:
a) can you
curl $my_ip:8775 (should 404)
CloudController and Nodes awnser in the same way:
1.0
2007-01-19
2007-03-01
2007-08-29
2007-10-10
2007-12-15
2008-02-01
2008-09-01
2009-04-04
b) if you do
sudo iptables -t nat -L -n v
do you see the forward rule? Is it getting hit properly?
there is the correct rule, but they never got hit
controller
0 0 DNAT tcp -- * * 0.0.0.0/0
169.254.169.254 tcp dpt:80 to:200.131.6.250:8775
nodes
0 0 DNAT tcp -- * * 0.0.0.0/0
169.254.169.254 tcp dpt:80 to:200.131.6.248:8775
0 0 DNAT tcp -- * * 0.0.0.0/0
169.254.169.254 tcp dpt:80 to:200.131.6.249:8775
Thanks for appearing Vish! I was wishing your help!
Vish
On Dec 19, 2012, at 6:39 AM, Gui Maluf guimal...@gmail.com wrote:
My set up is a
nova-network-hahttp://docs.openstack.org/trunk/openstack-compute/admin/content/existing-ha-networking-options.html,
so each of my nodes run a nova-{api-metadata,network,compute,volume}, my
controller runs all of this plus the rest of things it should run.
Each of my nodes are the gateway for it's own instances. They all have
the same net config, ip_forwarding.
The main issue is that I can't telnet the nodes on port 80 that should
redirect to metadatas server. metadata IP is set correctly to eth0, but 80
port is not open.
My doubt is, should I create a endpoint for each node api-metadata
service? should I install apache on nodes?
I really don't know what to do anymore. This only happen on nodes, on
cloudcontroller all instance run smoothly. they get the floatip, metadata
service, etc.
Thanks in advance!
I will put the max of info I can here.
root@oxala:~# nova-manage service
list
Binary Host Zone
Status State Updated_At
nova-compute xangonova
enabled:-) 2012-12-18 20:34:21
nova-network xangonova
enabled:-) 2012-12-18 20:34:20
nova-compute oxossi nova
enabled:-) 2012-12-18 20:34:15
nova-network oxossi nova
enabled:-) 2012-12-18 20:34:20
nova-volume oxossi nova
enabled:-) 2012-12-18 20:34:18
nova-volume xangonova
enabled:-) 2012-12-18 20:34:19
nova-consoleauth oxalanova
enabled:-) 2012-12-18 20:34:24
nova-scheduler oxalanova
enabled:-) 2012-12-18 20:34:25
nova-certoxalanova
enabled:-) 2012-12-18 20:34:25
nova-volume oxalanova
enabled:-) 2012-12-18 20:34:25
nova-network oxalanova
enabled:-) 2012-12-18 20:34:17
nova-compute oxalanova
enabled:-) 2012-12-18 20:34:10
*controller nova.conf*
#NETWORK
--allow_same_net_traffic=true
--network_manager=nova.network.manager.FlatDHCPManager
--firewall_driver=nova.virt.libvirt.firewall.IptablesFirewallDriver
--public_interface=eth0
--flat_interface=eth1
--flat_network_bridge=br100
--fixed_range=10.5.5.32/27
--network_size=32
[Openstack] Instances can't reach metadata server in network HA mode
My set up is a
nova-network-hahttp://docs.openstack.org/trunk/openstack-compute/admin/content/existing-ha-networking-options.html,
so each of my nodes run a nova-{api-metadata,network,compute,volume}, my
controller runs all of this plus the rest of things it should run.
Each of my nodes are the gateway for it's own instances. They all have the
same net config, ip_forwarding.
The main issue is that I can't telnet the nodes on port 80 that should
redirect to metadatas server. metadata IP is set correctly to eth0, but 80
port is not open.
My doubt is, should I create a endpoint for each node api-metadata service?
should I install apache on nodes?
I really don't know what to do anymore. This only happen on nodes, on
cloudcontroller all instance run smoothly. they get the floatip, metadata
service, etc.
Thanks in advance!
I will put the max of info I can here.
root@oxala:~# nova-manage service
list
Binary Host Zone
Status State Updated_At
nova-compute xangonova
enabled:-) 2012-12-18 20:34:21
nova-network xangonova
enabled:-) 2012-12-18 20:34:20
nova-compute oxossi nova
enabled:-) 2012-12-18 20:34:15
nova-network oxossi nova
enabled:-) 2012-12-18 20:34:20
nova-volume oxossi nova
enabled:-) 2012-12-18 20:34:18
nova-volume xangonova
enabled:-) 2012-12-18 20:34:19
nova-consoleauth oxalanova
enabled:-) 2012-12-18 20:34:24
nova-scheduler oxalanova
enabled:-) 2012-12-18 20:34:25
nova-certoxalanova
enabled:-) 2012-12-18 20:34:25
nova-volume oxalanova
enabled:-) 2012-12-18 20:34:25
nova-network oxalanova
enabled:-) 2012-12-18 20:34:17
nova-compute oxalanova
enabled:-) 2012-12-18 20:34:10
*controller nova.conf*
#NETWORK
--allow_same_net_traffic=true
--network_manager=nova.network.manager.FlatDHCPManager
--firewall_driver=nova.virt.libvirt.firewall.IptablesFirewallDriver
--public_interface=eth0
--flat_interface=eth1
--flat_network_bridge=br100
--fixed_range=10.5.5.32/27
--network_size=32
--flat_network_dhcp_start=10.5.5.33
--my_ip=200.131.6.250
--multi_host=True
#--enabled_apis=ec2,osapi_compute,osapi_volume,metadata
--dhcpbridge_flagfile=/etc/nova/nova.conf
--dhcpbridge=/usr/bin/nova-dhcpbridge
--force_dhcp_release
--ec2_private_dns_show
--routing_source_ip=$my_ip
*nodes nova.conf*
{same network configs}
--my_ip=200.131.6.248
--multi_host=True
--enabled_apis=ec2,osapi_compute,osapi_volume,metadata
--routing_source_ip=$my_ip
*controller iptables -L -vn **iptables -L -vn* *-t nat*
http://paste.openstack.org/show/mkWZTYI6cKHR4qUWbOUz/
*node* *iptables -L -vn **iptables -L -vn* *-t nat
*http://paste.openstack.org/show/28384/*
**
*
*controller ip a*
http://paste.openstack.org/show/W2vrVtost2EP2u62iZwp/
root@oxala:~# route
Tabela de Roteamento IP do Kernel
Destino RoteadorMáscaraGen.Opções Métrica Ref Uso
Iface
default 200.131.6.129 0.0.0.0 UG10000 eth0
10.5.5.32 * 255.255.255.224 U 0 00
br100
200.131.6.128 * 255.255.255.128 U 0 00 eth0
*node ip a
*http://paste.openstack.org/show/S44TL3sznIztNCO3s8p2/*
*root@oxossi:~# route
Tabela de Roteamento IP do Kernel
Destino RoteadorMáscaraGen.Opções Métrica Ref Uso
Iface
default 200.131.6.129 0.0.0.0 UG10000 eth0
10.5.5.32 * 255.255.255.224 U 0 00
br100
200.131.6.128 * 255.255.255.128 U 0 00 eth0
*
*
*And finnaly the error throw out by the vm when running on Nodes.
*
ci-info: lo: 1 127.0.0.1 255.0.0.0 .
ci-info: eth0 : 1 10.5.5.53 255.255.255.224 fa:16:3e:69:cb:d2
ci-info: route-0: 0.0.0.0 10.5.5.35 0.0.0.0 eth0 UG
ci-info: route-1: 10.5.5.32 0.0.0.0 255.255.255.224 eth0 U
cloud-init start running: Tue, 18 Dec 2012 20:34:09 +. up 4.02 seconds
2012-12-18 20:34:15,967 - util.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed
[6/120s]: url error [[Errno 113] No route to host]
--
*guilherme* \n
\t *maluf*
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Instances can't reach metadata server in network HA mode
On Wed, Dec 19, 2012 at 1:13 PM, Vishvananda Ishaya
vishvana...@gmail.comwrote:
There should be a redirect in iptables from 169.254.169.254:80 to
$my_ip:8775 (where nova-api-metadata is running)
So:
a) can you
curl $my_ip:8775 (should 404)
CloudController and Nodes awnser in the same way:
1.0
2007-01-19
2007-03-01
2007-08-29
2007-10-10
2007-12-15
2008-02-01
2008-09-01
2009-04-04
b) if you do
sudo iptables -t nat -L -n v
do you see the forward rule? Is it getting hit properly?
there is the correct rule, but they never got hit
controller
0 0 DNAT tcp -- * * 0.0.0.0/0
169.254.169.254 tcp dpt:80 to:200.131.6.250:8775
nodes
0 0 DNAT tcp -- * * 0.0.0.0/0
169.254.169.254 tcp dpt:80 to:200.131.6.248:8775
0 0 DNAT tcp -- * * 0.0.0.0/0
169.254.169.254 tcp dpt:80 to:200.131.6.249:8775
Thanks for appearing Vish! I was wishing your help!
Vish
On Dec 19, 2012, at 6:39 AM, Gui Maluf guimal...@gmail.com wrote:
My set up is a
nova-network-hahttp://docs.openstack.org/trunk/openstack-compute/admin/content/existing-ha-networking-options.html,
so each of my nodes run a nova-{api-metadata,network,compute,volume}, my
controller runs all of this plus the rest of things it should run.
Each of my nodes are the gateway for it's own instances. They all have the
same net config, ip_forwarding.
The main issue is that I can't telnet the nodes on port 80 that should
redirect to metadatas server. metadata IP is set correctly to eth0, but 80
port is not open.
My doubt is, should I create a endpoint for each node api-metadata
service? should I install apache on nodes?
I really don't know what to do anymore. This only happen on nodes, on
cloudcontroller all instance run smoothly. they get the floatip, metadata
service, etc.
Thanks in advance!
I will put the max of info I can here.
root@oxala:~# nova-manage service
list
Binary Host Zone
Status State Updated_At
nova-compute xangonova
enabled:-) 2012-12-18 20:34:21
nova-network xangonova
enabled:-) 2012-12-18 20:34:20
nova-compute oxossi nova
enabled:-) 2012-12-18 20:34:15
nova-network oxossi nova
enabled:-) 2012-12-18 20:34:20
nova-volume oxossi nova
enabled:-) 2012-12-18 20:34:18
nova-volume xangonova
enabled:-) 2012-12-18 20:34:19
nova-consoleauth oxalanova
enabled:-) 2012-12-18 20:34:24
nova-scheduler oxalanova
enabled:-) 2012-12-18 20:34:25
nova-certoxalanova
enabled:-) 2012-12-18 20:34:25
nova-volume oxalanova
enabled:-) 2012-12-18 20:34:25
nova-network oxalanova
enabled:-) 2012-12-18 20:34:17
nova-compute oxalanova
enabled:-) 2012-12-18 20:34:10
*controller nova.conf*
#NETWORK
--allow_same_net_traffic=true
--network_manager=nova.network.manager.FlatDHCPManager
--firewall_driver=nova.virt.libvirt.firewall.IptablesFirewallDriver
--public_interface=eth0
--flat_interface=eth1
--flat_network_bridge=br100
--fixed_range=10.5.5.32/27
--network_size=32
--flat_network_dhcp_start=10.5.5.33
--my_ip=200.131.6.250
--multi_host=True
#--enabled_apis=ec2,osapi_compute,osapi_volume,metadata
--dhcpbridge_flagfile=/etc/nova/nova.conf
--dhcpbridge=/usr/bin/nova-dhcpbridge
--force_dhcp_release
--ec2_private_dns_show
--routing_source_ip=$my_ip
*nodes nova.conf*
{same network configs}
--my_ip=200.131.6.248
--multi_host=True
--enabled_apis=ec2,osapi_compute,osapi_volume,metadata
--routing_source_ip=$my_ip
*controller iptables -L -vn **iptables -L -vn* *-t nat*
http://paste.openstack.org/show/mkWZTYI6cKHR4qUWbOUz/
*node* *iptables -L -vn **iptables -L -vn* *-t nat
*http://paste.openstack.org/show/28384/*
**
*
*controller ip a*
http://paste.openstack.org/show/W2vrVtost2EP2u62iZwp/
root@oxala:~# route
Tabela de Roteamento IP do Kernel
Destino RoteadorMáscaraGen.Opções Métrica Ref Uso
Iface
default 200.131.6.129 0.0.0.0 UG10000
eth0
10.5.5.32 * 255.255.255.224 U 0 00
br100
200.131.6.128 * 255.255.255.128 U 0 00
eth0
*node ip a
*http://paste.openstack.org/show/S44TL3sznIztNCO3s8p2/*
*root@oxossi:~# route
Tabela de Roteamento IP do Kernel
Destino RoteadorMáscaraGen.Opções Métrica Ref Uso
Iface
default 200.131.6.129 0.0.0.0 UG10000
eth0
10.5.5.32
Re: [Openstack] Instances can't reach metadata server in network HA mode
Yes, it's in multi_host=true. In nova.conf and in the database multi_host
is set to True. 10.5.5.32 isn't the gateway, instead is the private network.
LoL
Out of nothing my instances can now reach metadata. But when I login and
ping www.google.com VM can resolv name but there is no answer back, all
packets are lost. And I've attached a floating IP for two vms, on
different node, and they dont even ping back in the same node.
This is so confused! I'll do some tcpdump to check what is happening!
On Wed, Dec 19, 2012 at 2:05 PM, Vishvananda Ishaya
vishvana...@gmail.comwrote:
Are you sure your network has multi_host = True? It seems like it isn't,
since the gateway listed by the guest is 10.5.5.32
In multi_host mode each node should be getting an ip from the fixed range
and the guest should be using that as the gateway.
Vish
On Wed, Dec 19, 2012 at 1:13 PM, Vishvananda Ishaya vishvana...@gmail.com
wrote:
There should be a redirect in iptables from
169.254.169.254:80http://169.254.169.254/to $my_ip:8775 (where
nova-api-metadata is running)
So:
a) can you
curl $my_ip:8775 (should 404)
CloudController and Nodes awnser in the same way:
1.0
2007-01-19
2007-03-01
2007-08-29
2007-10-10
2007-12-15
2008-02-01
2008-09-01
2009-04-04
b) if you do
sudo iptables -t nat -L -n v
do you see the forward rule? Is it getting hit properly?
there is the correct rule, but they never got hit
controller
0 0 DNAT tcp -- * * 0.0.0.0/0
169.254.169.254 tcp dpt:80 to:200.131.6.250:8775
nodes
0 0 DNAT tcp -- * * 0.0.0.0/0
169.254.169.254 tcp dpt:80 to:200.131.6.248:8775
0 0 DNAT tcp -- * * 0.0.0.0/0
169.254.169.254 tcp dpt:80 to:200.131.6.249:8775
Thanks for appearing Vish! I was wishing your help!
Vish
On Dec 19, 2012, at 6:39 AM, Gui Maluf guimal...@gmail.com wrote:
My set up is a
nova-network-hahttp://docs.openstack.org/trunk/openstack-compute/admin/content/existing-ha-networking-options.html,
so each of my nodes run a nova-{api-metadata,network,compute,volume}, my
controller runs all of this plus the rest of things it should run.
Each of my nodes are the gateway for it's own instances. They all have
the same net config, ip_forwarding.
The main issue is that I can't telnet the nodes on port 80 that should
redirect to metadatas server. metadata IP is set correctly to eth0, but 80
port is not open.
My doubt is, should I create a endpoint for each node api-metadata
service? should I install apache on nodes?
I really don't know what to do anymore. This only happen on nodes, on
cloudcontroller all instance run smoothly. they get the floatip, metadata
service, etc.
Thanks in advance!
I will put the max of info I can here.
root@oxala:~# nova-manage service
list
Binary Host Zone
Status State Updated_At
nova-compute xangonova
enabled:-) 2012-12-18 20:34:21
nova-network xangonova
enabled:-) 2012-12-18 20:34:20
nova-compute oxossi nova
enabled:-) 2012-12-18 20:34:15
nova-network oxossi nova
enabled:-) 2012-12-18 20:34:20
nova-volume oxossi nova
enabled:-) 2012-12-18 20:34:18
nova-volume xangonova
enabled:-) 2012-12-18 20:34:19
nova-consoleauth oxalanova
enabled:-) 2012-12-18 20:34:24
nova-scheduler oxalanova
enabled:-) 2012-12-18 20:34:25
nova-certoxalanova
enabled:-) 2012-12-18 20:34:25
nova-volume oxalanova
enabled:-) 2012-12-18 20:34:25
nova-network oxalanova
enabled:-) 2012-12-18 20:34:17
nova-compute oxalanova
enabled:-) 2012-12-18 20:34:10
*controller nova.conf*
#NETWORK
--allow_same_net_traffic=true
--network_manager=nova.network.manager.FlatDHCPManager
--firewall_driver=nova.virt.libvirt.firewall.IptablesFirewallDriver
--public_interface=eth0
--flat_interface=eth1
--flat_network_bridge=br100
--fixed_range=10.5.5.32/27
--network_size=32
--flat_network_dhcp_start=10.5.5.33
--my_ip=200.131.6.250
--multi_host=True
#--enabled_apis=ec2,osapi_compute,osapi_volume,metadata
--dhcpbridge_flagfile=/etc/nova/nova.conf
--dhcpbridge=/usr/bin/nova-dhcpbridge
--force_dhcp_release
--ec2_private_dns_show
--routing_source_ip=$my_ip
*nodes nova.conf*
{same network configs}
--my_ip=200.131.6.248
--multi_host=True
--enabled_apis=ec2,osapi_compute,osapi_volume,metadata
--routing_source_ip=$my_ip
*controller iptables -L -vn **iptables -L -vn* *-t nat*
http
[Openstack] Running crazy with Essex, multi_host, nova-network-ha, nova-api-metadata, VMs can't reach metadata nor respond through floating ip
Countless times I'm here trying to make my openstack runnig! So here we go
again!
My set up is a
nova-network-hahttp://docs.openstack.org/trunk/openstack-compute/admin/content/existing-ha-networking-options.html,
so each of my nodes run a nova-{api-metadata,network,compute,volume}, my
controller runs all of this and the rest of things it should run.
So I'm facing many problems in my setup. The main thing is: iptables rules
are meaningless, they just doesnt work. VMs can't reach metadata, and
floating ip SNAT/DNAT is not pointing to VM.
I will put the max of info I can here.
root@oxala:~# nova-manage service
list
Binary Host Zone
Status State Updated_At
nova-compute xangonova
enabled:-) 2012-12-18 20:34:21
nova-network xangonova
enabled:-) 2012-12-18 20:34:20
nova-compute oxossi nova
enabled:-) 2012-12-18 20:34:15
nova-network oxossi nova
enabled:-) 2012-12-18 20:34:20
nova-volume oxossi nova
enabled:-) 2012-12-18 20:34:18
nova-volume xangonova
enabled:-) 2012-12-18 20:34:19
nova-consoleauth oxalanova
enabled:-) 2012-12-18 20:34:24
nova-scheduler oxalanova
enabled:-) 2012-12-18 20:34:25
nova-certoxalanova
enabled:-) 2012-12-18 20:34:25
nova-volume oxalanova
enabled:-) 2012-12-18 20:34:25
nova-network oxalanova
enabled:-) 2012-12-18 20:34:17
nova-compute oxalanova
enabled:-) 2012-12-18 20:34:10
*controller nova.conf*
#NETWORK
--allow_same_net_traffic=true
--network_manager=nova.network.manager.FlatDHCPManager
--firewall_driver=nova.virt.libvirt.firewall.IptablesFirewallDriver
--public_interface=eth0
--flat_interface=eth1
--flat_network_bridge=br100
--fixed_range=10.5.5.32/27
--network_size=32
--flat_network_dhcp_start=10.5.5.33
--my_ip=200.131.6.250
--multi_host=True
#--enabled_apis=ec2,osapi_compute,osapi_volume,metadata
--dhcpbridge_flagfile=/etc/nova/nova.conf
--dhcpbridge=/usr/bin/nova-dhcpbridge
--force_dhcp_release
--ec2_private_dns_show
--routing_source_ip=$my_ip
*nodes nova.conf*
{same network configs}
--my_ip=200.131.6.248
--multi_host=True
--enabled_apis=ec2,osapi_compute,osapi_volume,metadata
--routing_source_ip=$my_ip
***controller iptables -L -vn **iptables -L -vn* *-t nat*
http://paste.openstack.org/show/mkWZTYI6cKHR4qUWbOUz/
*node* *iptables -L -vn **iptables -L -vn* *-t nat
*http://paste.openstack.org/show/28384/*
**
*
*controller ip a*
http://paste.openstack.org/show/W2vrVtost2EP2u62iZwp/
root@oxala:~# route
Tabela de Roteamento IP do Kernel
Destino RoteadorMáscaraGen.Opções Métrica Ref Uso
Iface
default 200.131.6.129 0.0.0.0 UG10000 eth0
10.5.5.32 * 255.255.255.224 U 0 00
br100
200.131.6.128 * 255.255.255.128 U 0 00 eth0
*node ip a
*http://paste.openstack.org/show/S44TL3sznIztNCO3s8p2/*
*root@oxossi:~# route
Tabela de Roteamento IP do Kernel
Destino RoteadorMáscaraGen.Opções Métrica Ref Uso
Iface
default 200.131.6.129 0.0.0.0 UG10000 eth0
10.5.5.32 * 255.255.255.224 U 0 00
br100
200.131.6.128 * 255.255.255.128 U 0 00 eth0
*
*
*And finnaly the error throw out by the vm when running on Nodes.
*
ci-info: lo: 1 127.0.0.1 255.0.0.0 .
ci-info: eth0 : 1 10.5.5.53 255.255.255.224 fa:16:3e:69:cb:d2
ci-info: route-0: 0.0.0.0 10.5.5.35 0.0.0.0 eth0 UG
ci-info: route-1: 10.5.5.32 0.0.0.0 255.255.255.224 eth0 U
cloud-init start running: Tue, 18 Dec 2012 20:34:09 +. up 4.02 seconds
2012-12-18 20:34:15,967 - util.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed
[6/120s]: url error [[Errno 113] No route to host]
I really don't know what to do anymore. This only happen on nodes, on
cloudcontroller all instance run smoothly. they get the floatip, metadata
service, etc.
I thought the nova-network-HA would give me less headache but is happening
the opposite. I would really appreciate if someone could help me!
Thanks in advance!
--
*guilherme* \n
\t *maluf*
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
[Openstack] [urgent] Nova-network isn't creating floating IP iptables rules!
Hey guys. I think I did a stupid thing. My setup is 1 cloudcontroller + node and 2 node with FlatDHCP, mult_host, net HA. Recently I've changed the hostname of my cloudcontroller; to make things consistent I've updated the services table inside nova db to mark as deleted=1 the lines where host=oldhostname. I dont know what happened because now nothing of the nova-network works. It doesn't create br100 anymore, neither iptables rules of SNAT and DNAT The worse thing about that problem, is that this is production setup. All my instances from the cloudcontroller are unavaible cause of this. Nodes are creating everything regularly I couldn't found nothing wrong on logs, no errors. Anyway, here are my logs and setup files. controller nova.conf: http://paste.openstack.org/show/28095/ node nova.conf: http://paste.openstack.org/show/28096/ iptables -L -t nat + brctl show + virsh list: http://paste.openstack.org/show/28098/ Any other information please let me know! I need to fix this ASAP -- *guilherme* \n \t *maluf* ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [urgent] Nova-network isn't creating floating IP iptables rules!
Razique, thanks for the tip.
To find out which tables has the hostname set I did this:
# for i in `mysql -uroot -p'PASSWORD' -e 'show tables;' nova | grep -v -e
'+' -e 'T'`; do echo $i mysql -uroot -p'PASSWORD' -e select * from
$i;' nova | grep OLD_HOSTNAME; done
This will print many data with the name of the tables and after all
occurrences of the HOSTNAME inside the tables.
Then I've changed all host to the correct hostname
# for i in {187..190} 193 195; do mysql -uroot -p'PASSWORD' -e update
TABLE set host=NEW_HOSTNAME where id =$i; nova; done
i.e: # for i in {187..190} 193 195; do mysql -uroot -p'PASSWORD' -e update
floating_ips set host='oxala' where id =$i; nova; done
Thanks man! it solved my a part of my issue.
On Fri, Dec 14, 2012 at 12:59 PM, Razique Mahroua razique.mahr...@gmail.com
wrote:
Check the nova database, the network tables and fixed_ip contains the
hostname.
Update these fields too and you should be ok :)
(Maybe your /etc/hosts files, keystone endpoints if you used hostnames)
*Razique Mahroua** - **Nuage Co*
razique.mahr...@gmail.com
Tel : +33 9 72 37 94 15
Le 14 déc. 2012 à 15:43, Gui Maluf guimal...@gmail.com a écrit :
Hey guys. I think I did a stupid thing.
My setup is 1 cloudcontroller + node and 2 node with FlatDHCP, mult_host,
net HA.
Recently I've changed the hostname of my cloudcontroller; to make things
consistent I've updated the services table inside nova db to mark as
deleted=1 the lines where host=oldhostname.
I dont know what happened because now nothing of the nova-network works.
It doesn't create br100 anymore, neither iptables rules of SNAT and DNAT
The worse thing about that problem, is that this is production setup. All
my instances from the cloudcontroller are unavaible cause of this. Nodes
are creating everything regularly
I couldn't found nothing wrong on logs, no errors. Anyway, here are my
logs and setup files.
controller nova.conf: http://paste.openstack.org/show/28095/
node nova.conf: http://paste.openstack.org/show/28096/
iptables -L -t nat + brctl show + virsh list:
http://paste.openstack.org/show/28098/
Any other information please let me know!
I need to fix this ASAP
--
*guilherme* \n
\t *maluf*
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
--
*guilherme* \n
\t *maluf*
NUAGECO-LOGO-Fblan_petit.jpg___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [urgent] Nova-network isn't creating floating IP iptables rules!
I don't know if it is related to this hostname issue, but my nova-compute
on cloudcontroller can't initiate an iscsi volume in the same controller.
2012-12-14 14:13:46 DEBUG nova.utils
[req-98c1f3b8-ac10-4aa6-a806-f2dd18928af2 None None] Result was 255 from
(pid=5250) execute /usr/lib/python2.7/dist-packages/nova/utils.py:235
2012-12-14 14:13:46 CRITICAL nova [-] Unexpected error while running
command.
Command: sudo nova-rootwrap iscsiadm -m node -T
iqn.2010-10.org.openstack:volume-0006 -p 200.131.6.250:3260 --rescan
Exit code: 255
2012-12-14 14:13:46 TRACE nova ProcessExecutionError: Unexpected error
while running command.
2012-12-14 14:13:46 TRACE nova Command: sudo nova-rootwrap iscsiadm -m node
-T iqn.2010-10.org.openstack:volume-0006 -p 200.131.6.250:3260 --rescan
2012-12-14 14:13:46 TRACE nova Exit code: 255
2012-12-14 14:13:46 TRACE nova Stdout:
2012-12-14 14:13:46 TRACE nova Stderr: 'iscsiadm: No portal found.\n'
fulll nova-compute.log: http://paste.openstack.org/show/28109/
On Fri, Dec 14, 2012 at 1:45 PM, Gui Maluf guimal...@gmail.com wrote:
Razique, thanks for the tip.
To find out which tables has the hostname set I did this:
# for i in `mysql -uroot -p'PASSWORD' -e 'show tables;' nova | grep -v -e
'+' -e 'T'`; do echo $i mysql -uroot -p'PASSWORD' -e select * from
$i;' nova | grep OLD_HOSTNAME; done
This will print many data with the name of the tables and after all
occurrences of the HOSTNAME inside the tables.
Then I've changed all host to the correct hostname
# for i in {187..190} 193 195; do mysql -uroot -p'PASSWORD' -e update
TABLE set host=NEW_HOSTNAME where id =$i; nova; done
i.e: # for i in {187..190} 193 195; do mysql -uroot -p'PASSWORD' -e
update floating_ips set host='oxala' where id =$i; nova; done
Thanks man! it solved my a part of my issue.
On Fri, Dec 14, 2012 at 12:59 PM, Razique Mahroua
razique.mahr...@gmail.com wrote:
Check the nova database, the network tables and fixed_ip contains the
hostname.
Update these fields too and you should be ok :)
(Maybe your /etc/hosts files, keystone endpoints if you used hostnames)
*Razique Mahroua** - **Nuage Co*
razique.mahr...@gmail.com
Tel : +33 9 72 37 94 15
Le 14 déc. 2012 à 15:43, Gui Maluf guimal...@gmail.com a écrit :
Hey guys. I think I did a stupid thing.
My setup is 1 cloudcontroller + node and 2 node with FlatDHCP, mult_host,
net HA.
Recently I've changed the hostname of my cloudcontroller; to make things
consistent I've updated the services table inside nova db to mark as
deleted=1 the lines where host=oldhostname.
I dont know what happened because now nothing of the nova-network works.
It doesn't create br100 anymore, neither iptables rules of SNAT and DNAT
The worse thing about that problem, is that this is production setup.
All my instances from the cloudcontroller are unavaible cause of this.
Nodes are creating everything regularly
I couldn't found nothing wrong on logs, no errors. Anyway, here are my
logs and setup files.
controller nova.conf: http://paste.openstack.org/show/28095/
node nova.conf: http://paste.openstack.org/show/28096/
iptables -L -t nat + brctl show + virsh list:
http://paste.openstack.org/show/28098/
Any other information please let me know!
I need to fix this ASAP
--
*guilherme* \n
\t *maluf*
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
--
*guilherme* \n
\t *maluf*
--
*guilherme* \n
\t *maluf*
NUAGECO-LOGO-Fblan_petit.jpg___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
Re: [Openstack] nova boot errors while attaching a volume to an instance
I found the problem. Ubuntu MAAS iscsi images were occupying the target_num of the iscsi volumes. I just removed the iscsi disks and worked well! On Fri, Dec 14, 2012 at 3:21 PM, Gui Maluf guimal...@gmail.com wrote: I'm running the same problem! And I would be grateful if someone could help me! root@oxala:/var/log/nova# iscsiadm -m node 200.131.6.250:3260,1 iqn.2004-05.com.ubuntu:maas:maas-precise-12.04-i386-ephemeral-20120424 10.5.5.35:3260,1 iqn.2004-05.com.ubuntu:maas:maas-precise-12.04-i386-ephemeral-20120424 200.131.6.250:3260,1 iqn.2004-05.com.ubuntu:maas:maas-precise-12.04-amd64-ephemeral-20120424 10.5.5.35:3260,1 iqn.2004-05.com.ubuntu:maas:maas-precise-12.04-amd64-ephemeral-20120424 200.131.6.250:3260,-1 iqn.2010-10.org.openstack:volume-0006 150.164.3.236:3260,-1 iqn.2010-10.org.openstack:volume-0002 200.131.6.250:3260,-1 iqn.2010-10.org.openstack:volume-0005 When I'm running iscsadm -m node all my openstack-volumes got this strange -1 (node.tpgt = -1). I've tried to create the iscsi target by hand, but I couldnt. If some could help me! Here is my fulll nova-compute.log: http://paste.openstack.org/show/28109/ Thanks in advance On Wed, Oct 31, 2012 at 6:14 PM, John Griffith john.griff...@solidfire.com wrote: On Wed, Oct 31, 2012 at 1:29 PM, Bontala, Vibhuvardhan vibhuvardhan.bont...@emc.com wrote: Hi, ** ** I am running GA bits of Folsom. I am running a two node setup where the first node is the controller+compute node that has Cinder running as well. The second node is merely a compute node. I am seeing an issue while booting an instance from Cinder volume on both the nodes. The “nova boot” operation fails while spawning the instance with the following error.*** * ** ** [00mProcessExecutionError: Unexpected error while running command. [00mCommand: sudo nova-rootwrap /etc/nova/rootwrap.conf iscsiadm -m node -T iqn.2010-10.org.openstack:volume-3ac4b027-905e-4318-a74e-2bdf94f5d887 -p 192.168.150.96:3260 --rescan [00mExit code: 255 [00mStdout: '' [00mStderr: 'iscsiadm: No portal found.\n' [00m ** ** I had successfully created a Cinder volume with a valid image on it. ** ** +--+---+--+--+-+-+ | ID | Status | Display Name | Size | Volume Type | Attached to | +--+---+--+--+-+-+ | 3ac4b027-905e-4318-a74e-2bdf94f5d887 | available | Volume1| 2 | None| | +--+---+--+--+-+-+ ** ** I even tried to discover the iSCSI targets. But it returns with “no records found”. ** ** I then looked into to MySQL database for Cinder and looked at the entries, specifically “provider_location” and it looked just fine. 192.168.150.96 is the node where I have controller and cinder running.** ** ** ** +---+ | provider_location | +---+ | NULL | | 192.168.150.96:3260,1 iqn.2010-10.org.openstack:volume-3ac4b027-905e-4318-a74e-2bdf94f5d887 1 | ** ** I manually tried to discover the iSCSI targets and it couldn’t find any. ** ** stack@esg-dell-c4-s08:/etc/cinder$ sudo iscsiadm -m discovery -t sendtargets -p 192.168.150.96:3260 192.168.150.96:3260,1 iqn.2010-10.org.openstack:volume-3ac4b027-905e-4318-a74e-2bdf94f5d887*** * iscsiadm: Connection to Discovery Address 192.168.150.96 closed iscsiadm: Login I/O error, failed to receive a PDU iscsiadm: retrying discovery login to 192.168.150.96 stack@esg-dell-c4-s08:/etc/cinder$ sudo iscsiadm -m node -T iqn.2010-10.org.openstack:volume-3ac4b027-905e-4318-a74e-2bdf94f5d887 -p 192.168.150.96:3260iscsiadm: no records found! stack@esg-dell-c4-s08:/etc/cinder$ sudo iscsiadm -m node -T iqn.2010-10.org.openstack:volume-3ac4b027-905e-4318-a74e-2bdf94f5d887 -p 192.168.150.96:3260 --rescan iscsiadm: No portal found. stack@esg-dell-c4-s08:/etc/cinder$ ** ** I am not sure what’s wrong with my setup. Any help is greatly appreciated. ** ** Thanks Vibhu ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp Hi Vibnu, Strange, you're unable to see the target on either of the nodes? I'm assuming your using the default LVM storage back-end. Something to look at: sudo tgtadm --lld iscsi --op show --mode target - Make sure your
Re: [Openstack] nova-compute not starting
anytime this happend with me I do the following. create a lost_instance.xml with the content below(I think it's possible to create a simpler file, with less content) just to register a VM with libvirt. Make sure to change the name/name tag. In your case domain type='kvm' nameinstance-002a/name memory unit='KiB'4194304/memory currentMemory unit='KiB'4194304/currentMemory vcpu placement='static'4/vcpu os type arch='x86_64' machine='pc-1.0'hvm/type boot dev='hd'/ /os features acpi/ apic/ pae/ /features clock offset='utc'/ on_poweroffdestroy/on_poweroff on_rebootrestart/on_reboot on_crashrestart/on_crash devices emulator/usr/bin/kvm/emulator controller type='ide' index='0' address type='pci' domain='0x' bus='0x00' slot='0x01' function='0x1'/ /controller controller type='usb' index='0' address type='pci' domain='0x' bus='0x00' slot='0x01' function='0x2'/ /controller serial type='pty' target port='0'/ /serial console type='pty' target type='serial' port='0'/ /console input type='mouse' bus='ps2'/ graphics type='vnc' port='-1' autoport='yes'/ video model type='cirrus' vram='9216' heads='1'/ address type='pci' domain='0x' bus='0x00' slot='0x02' function='0x0'/ /video memballoon model='virtio' address type='pci' domain='0x' bus='0x00' slot='0x04' function='0x0'/ /memballoon /devices /domain save and exit and then # virsh define lost_instance.xml # service nova-compute restart it's easier then mess with the database. On Thu, Dec 13, 2012 at 8:56 AM, Razique Mahroua razique.mahr...@gmail.comwrote: I think the instance ID is the database ID (base 8) encoded in base 16. 0x2A = ID 52 into the database. Did you updated the ID 52 ? I may be wrong ^^ *Razique Mahroua** - **Nuage Co* razique.mahr...@gmail.com Tel : +33 9 72 37 94 15 Le 13 déc. 2012 à 11:51, Joe Warren-Meeks joe.warren.me...@gmail.com a écrit : It turned out to be that last one. What I don't understand is where openstack found the instance id from. That doesn't exist in the database, or anywhere on the file system I could find. Kind regards -- joe. On 13 December 2012 10:27, Razique Mahroua razique.mahr...@gmail.comwrote: Hey Joe, yes, several solutions there First, check if the domain exists by running $ virsh list --all (supposing you use libvirt) check /var/lib/nova/instances/instance-002a if the dir. exists $cd into it and run virsh define libvirt.xml then restart nova-compute If the dir. doesn't exist, you may want to update the nova database, figure out your instance entry within the instances table and update the field deleted to 1 Regards, *Razique Mahroua** - **Nuage Co* razique.mahr...@gmail.com Tel : +33 9 72 37 94 15 NUAGECO-LOGO-Fblan_petit.jpg Le 12 déc. 2012 à 17:07, Joe Warren-Meeks joe.warren.me...@gmail.com a écrit : Hi guys, You think you have Openstack working, then you cough and it all breaks. I'm getting the following error when trying to start nova-compute after a reboot of the compute node (to install non-related patches) libvirtError: Domain not found: no domain with matching name 'instance-002a' Now, I've dumped all the DBs to disk and grepped through it for '2a' and grep -R'ed /etc/ and /var/ I can't find any reference to that anywhere, but it is causing nova-compute to fail to start. Anyone know how to fix that? If not, anyone know a cloud platform that isn't made from very thin glass, pre-shattered for your pleasure? -- joe. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- *guilherme* \n \t *maluf* NUAGECO-LOGO-Fblan_petit.jpg___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] 2 Questions: Port 5000 and 35357, glance index
I think 5000 is kind of public port, for external use, and 35357 a private port for internal use. But probably I'm wrong! :) Is your OS_AUTH_URL and SERVICE_ENDPOINT defined? unset one of them and try again. On Thu, Dec 13, 2012 at 12:54 AM, Hao Wang hao.1.w...@gmail.com wrote: Hi Stackers, What is the difference between the ports 5000 and 35357? When I run glance command, the error message is as below. I googled the message, but no results can address this issue. root@Controller:~# glance index ID Name Disk Format Container Format Size -- -- Error communicating with /v1/images/detail?limit=10: [Errno 111] Connection refused Thanks, Howard ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- *guilherme* \n \t *maluf* ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Installing Openstack - Issue with Keystone
I ran into this problem, it's cause by two env variable defined. Try to unset the OS_TOKEN variable you are using OS_USERNAME or unset SERVICE_ENDPOINT and SERVICE_TOKEN if you are using OS_AUTH_URL On Fri, Dec 7, 2012 at 1:49 PM, Wojciech Dec wdec.i...@gmail.com wrote: Hi All, while following the Openstack Install guide (all using regular repo commands) on an Ubuntu 12.04 system I ran into the following problem with Keystone: Pretty much any command entered gives the following error. host1:~$keystone user-role-add --user aba --role xxx --tenant_id 1 Expecting authentication method via either a service token, --token or env[SERVICE_TOKEN], or credentials, --os_username or env[OS_USERNAME]. Any clues/solutions? Thanks. W. Dec ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- *guilherme* \n \t *maluf* ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] 500 Internal Server error and [Errno 113] EHOSTUNREACH when adding a new node
Andrew, you're right. I just set up the swift + glance integration and
uploaded again the image! everything worked fine! :D
On Tue, Dec 4, 2012 at 1:55 PM, Gui Maluf guimal...@gmail.com wrote:
I've change the default_store to file on glance-api.conf
even after changin this I'm getting the same error related to swift!
On Tue, Dec 4, 2012 at 1:45 PM, Razique Mahroua razique.mahr...@gmail.com
wrote:
Oh my bad, I misread.
Let us know how it's going with Andrew's tip :)
*Razique Mahroua** - **Nuage Co*
razique.mahr...@gmail.com
Tel : +33 9 72 37 94 15
Le 4 déc. 2012 à 16:22, Gui Maluf guimal...@gmail.com a écrit :
On Tue, Dec 4, 2012 at 1:16 PM, Razique Mahroua
razique.mahr...@gmail.com wrote:
*Razique Mahroua** - **Nuage Co*
razique.mahr...@gmail.com
Tel : +33 9 72 37 94 15
NUAGECO-LOGO-Fblan_petit.jpg
Le 4 déc. 2012 à 16:01, Gui Maluf guimal...@gmail.com a écrit :
Hy, I've a ubuntu 12.04 cloud controller + node runing essex in
multi_node mode.
So I'm trying to install a new node but without success.
Node and controller have the same /etc/network/interface/;
You mean they both have the same IP address ?
Course not. All machines have different IP.
Node is running nova-{api-metadata,compute,network,volume};
nova.conf: http://paste.openstack.org/show/27390/
Node have this line above uncommented and --my_ip changed
--enabled_apis=ec2,osapi_compute,osapi_volume,metadata
Here is the nova-compute.log: http://paste.openstack.org/show/27387/with
complete error.
I'm trying to install two nodes, and from both I can reach all services
on cloud-controller.
telnet cloud-controller 9292 works from both nodes. They all have the
same nova.conf. I dont know what else can be this error.
I've check many things and I cant find a solution to this.
Thanks in advance!
--
*guilherme* \n
\t *maluf*
Is keystone running ?
What $ keystone user-list shows ?
the whole cloud-controller-node works fine. keystone, vm, network,
volume. The step of adding nodes is not working! I'm trying to remember
anything I'd done. And the only think I can remeber is that I've changed
the hostname of the CC-node.
I dont know how this can affect the whole system and wherelse get more
info about this issue!
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
Regards,
Razique
--
*guilherme* \n
\t *maluf*
--
*guilherme* \n
\t *maluf*
--
*guilherme* \n
\t *maluf*
NUAGECO-LOGO-Fblan_petit.jpg___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
[Openstack] 500 Internal Server error and [Errno 113] EHOSTUNREACH when adding a new node
Hy, I've a ubuntu 12.04 cloud controller + node runing essex in multi_node
mode.
So I'm trying to install a new node but without success.
Node and controller have the same /etc/network/interface/;
Node is running nova-{api-metadata,compute,network,volume};
nova.conf: http://paste.openstack.org/show/27390/
Node have this line above uncommented and --my_ip changed
--enabled_apis=ec2,osapi_compute,osapi_volume,metadata
Here is the nova-compute.log: http://paste.openstack.org/show/27387/ with
complete error.
I'm trying to install two nodes, and from both I can reach all services on
cloud-controller.
telnet cloud-controller 9292 works from both nodes. They all have the same
nova.conf. I dont know what else can be this error.
I've check many things and I cant find a solution to this.
Thanks in advance!
--
*guilherme* \n
\t *maluf*
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
Re: [Openstack] 500 Internal Server error and [Errno 113] EHOSTUNREACH when adding a new node
On Tue, Dec 4, 2012 at 1:16 PM, Razique Mahroua
razique.mahr...@gmail.comwrote:
*Razique Mahroua** - **Nuage Co*
razique.mahr...@gmail.com
Tel : +33 9 72 37 94 15
Le 4 déc. 2012 à 16:01, Gui Maluf guimal...@gmail.com a écrit :
Hy, I've a ubuntu 12.04 cloud controller + node runing essex in multi_node
mode.
So I'm trying to install a new node but without success.
Node and controller have the same /etc/network/interface/;
You mean they both have the same IP address ?
Course not. All machines have different IP.
Node is running nova-{api-metadata,compute,network,volume};
nova.conf: http://paste.openstack.org/show/27390/
Node have this line above uncommented and --my_ip changed
--enabled_apis=ec2,osapi_compute,osapi_volume,metadata
Here is the nova-compute.log: http://paste.openstack.org/show/27387/ with
complete error.
I'm trying to install two nodes, and from both I can reach all services on
cloud-controller.
telnet cloud-controller 9292 works from both nodes. They all have the same
nova.conf. I dont know what else can be this error.
I've check many things and I cant find a solution to this.
Thanks in advance!
--
*guilherme* \n
\t *maluf*
Is keystone running ?
What $ keystone user-list shows ?
the whole cloud-controller-node works fine. keystone, vm, network, volume.
The step of adding nodes is not working! I'm trying to remember anything
I'd done. And the only think I can remeber is that I've changed the
hostname of the CC-node.
I dont know how this can affect the whole system and wherelse get more info
about this issue!
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
Regards,
Razique
--
*guilherme* \n
\t *maluf*
NUAGECO-LOGO-Fblan_petit.jpg___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
Re: [Openstack] 500 Internal Server error and [Errno 113] EHOSTUNREACH when adding a new node
I've change the default_store to file on glance-api.conf
even after changin this I'm getting the same error related to swift!
On Tue, Dec 4, 2012 at 1:45 PM, Razique Mahroua
razique.mahr...@gmail.comwrote:
Oh my bad, I misread.
Let us know how it's going with Andrew's tip :)
*Razique Mahroua** - **Nuage Co*
razique.mahr...@gmail.com
Tel : +33 9 72 37 94 15
Le 4 déc. 2012 à 16:22, Gui Maluf guimal...@gmail.com a écrit :
On Tue, Dec 4, 2012 at 1:16 PM, Razique Mahroua razique.mahr...@gmail.com
wrote:
*Razique Mahroua** - **Nuage Co*
razique.mahr...@gmail.com
Tel : +33 9 72 37 94 15
NUAGECO-LOGO-Fblan_petit.jpg
Le 4 déc. 2012 à 16:01, Gui Maluf guimal...@gmail.com a écrit :
Hy, I've a ubuntu 12.04 cloud controller + node runing essex in
multi_node mode.
So I'm trying to install a new node but without success.
Node and controller have the same /etc/network/interface/;
You mean they both have the same IP address ?
Course not. All machines have different IP.
Node is running nova-{api-metadata,compute,network,volume};
nova.conf: http://paste.openstack.org/show/27390/
Node have this line above uncommented and --my_ip changed
--enabled_apis=ec2,osapi_compute,osapi_volume,metadata
Here is the nova-compute.log: http://paste.openstack.org/show/27387/with
complete error.
I'm trying to install two nodes, and from both I can reach all services
on cloud-controller.
telnet cloud-controller 9292 works from both nodes. They all have the
same nova.conf. I dont know what else can be this error.
I've check many things and I cant find a solution to this.
Thanks in advance!
--
*guilherme* \n
\t *maluf*
Is keystone running ?
What $ keystone user-list shows ?
the whole cloud-controller-node works fine. keystone, vm, network, volume.
The step of adding nodes is not working! I'm trying to remember anything
I'd done. And the only think I can remeber is that I've changed the
hostname of the CC-node.
I dont know how this can affect the whole system and wherelse get more
info about this issue!
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
Regards,
Razique
--
*guilherme* \n
\t *maluf*
--
*guilherme* \n
\t *maluf*
NUAGECO-LOGO-Fblan_petit.jpg___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Error while enabling s3 support in swift
John, I installed the fujita/swift3 but I'm stuck at this point:
Traceback (most recent call last):
File /usr/bin/swift-proxy-server, line 22, in module
run_wsgi(conf_file, 'proxy-server', default_port=8080, **options)
File /usr/lib/python2.7/dist-packages/swift/common/wsgi.py, line 138,
in run_wsgi
loadapp('config:%s' % conf_file, global_conf={'log_name': log_name})
File /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line
247, in loadapp
return loadobj(APP, uri, name=name, **kw)
File /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line
271, in loadobj
global_conf=global_conf)
File /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line
296, in loadcontext
global_conf=global_conf)
File /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line
320, in _loadconfig
return loader.get_context(object_type, name, global_conf)
File /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line
450, in get_context
global_additions=global_additions)
File /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line
562, in _pipeline_app_context
for name in pipeline[:-1]]
File /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line
454, in get_context
section)
File /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line
476, in _context_from_use
object_type, name=use, global_conf=global_conf)
File /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line
406, in get_context
global_conf=global_conf)
File /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line
296, in loadcontext
global_conf=global_conf)
File /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line
328, in _loadegg
return loader.get_context(object_type, name, global_conf)
File /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line
620, in get_context
object_type, name=name)
File /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line
646, in find_egg_entry_point
possible.append((entry.load(), protocol, entry.name))
File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 1989, in
load
entry = __import__(self.module_name, globals(),globals(), ['__name__'])
File
/usr/local/lib/python2.7/dist-packages/swift3-1.0.0-py2.7.egg/swift3/middleware.py,
line 67, in
module
from swift.common.swob import Request, Response
ImportError: No module named swob
I couldnt find a way to install this swob module.
Any hint?
On Tue, Nov 20, 2012 at 5:46 AM, Shashank Sahni shredde...@gmail.comwrote:
I haven't tested but the proxy server has started fine. Thanks.
--
Shashank Sahni
On Tue, Nov 20, 2012 at 12:55 PM, John Dickinson m...@not.mn wrote:
check out the README at https://github.com/fujita/swift3 for the correct
proxy server config section.
--john
On Nov 19, 2012, at 11:22 PM, Shashank Sahni shredde...@gmail.com
wrote:
Hi,
I'm trying to install swift 1.7.4 on Ubuntu 12.04. In order to enable
the s3 support, I added the appropriate parameters in the
/etc/swift/proxy-server.conf file
[filter:swift3]
use=egg:swift#swift3
and installed the package swift-plugin-s3. But when I try to start the
proxy-server I get the following error.
LookupError: Entry point 'swift3' not found in egg 'swift' (dir:
/usr/lib/python2.7/dist-packages; protocols: paste.filter_factory,
paste.filter_app_factory; entry_points: )
Note that, proxy server runs fine without s3 support. Suggestions?
--
Shashank Sahni
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
--
*guilherme* \n
\t *maluf*
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Error while enabling s3 support in swift
Thanks Alan. I did # git checkout 195e6c7 -- swift3/middleware.py # python setup.py install and proxy started fine! :) thanks On Wed, Nov 28, 2012 at 10:32 AM, Alan Pevec ape...@gmail.com wrote: 2012/11/28 Gui Maluf guimal...@gmail.com: /usr/local/lib/python2.7/dist-packages/swift3-1.0.0-py2.7.egg/swift3/middleware.py, line 67, in module from swift.common.swob import Request, Response ImportError: No module named swob I couldnt find a way to install this swob module. You need Swift 1.7.5 or use older swift3 before https://github.com/fujita/swift3/commit/6429b1c5b97fd61452e1d3e66d0af17302922d8b Cheers, Alan ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- *guilherme* \n \t *maluf* ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [devstack] How to purge, remove and wipe out devstack?
I'll try this Joshua, thanks! On Mon, Nov 19, 2012 at 4:25 PM, Joshua Harlow harlo...@yahoo-inc.comwrote: U can try anvil http://anvil.readthedocs.org/en/latest/ also, its similar but I built it with the goal to do uninstalls/starts/stops from the start. Your mileage may vary though :-) -Josh From: Tong Li liton...@us.ibm.com Date: Monday, November 19, 2012 6:19 AM To: Gui Maluf guimal...@gmail.com Cc: openstack-bounces+litong01=us.ibm@lists.launchpad.net openstack-bounces+litong01=us.ibm@lists.launchpad.net, openstack@lists.launchpad.net openstack@lists.launchpad.net Subject: Re: [Openstack] [devstack] How to purge, remove and wipe out devstack? There are configuration files under /etc for components that you enabled when you install devstack. such as /etc/nova, /etc/glance, etc. Tong Li Emerging Technologies Standards [image: Inactive hide details for Gui Maluf ---11/19/2012 05:10:27 AM---Hello, if I would like to wipe, remove and purge everything dev]Gui Maluf ---11/19/2012 05:10:27 AM---Hello, if I would like to wipe, remove and purge everything devstack installed and From: Gui Maluf guimal...@gmail.com To: openstack@lists.launchpad.net openstack@lists.launchpad.net, Date: 11/19/2012 05:10 AM Subject: [Openstack] [devstack] How to purge, remove and wipe out devstack? Sent by: openstack-bounces+litong01=us.ibm@lists.launchpad.net -- Hello, if I would like to wipe, remove and purge everything devstack installed and configured what should I do? rm -rf /opt/stack rm -rf /usr/local/bin/ what else? thanks in advance! :) -- * guilherme* \n \t *maluf* ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- *guilherme* \n \t *maluf* graycol.gif___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] [devstack] How to purge, remove and wipe out devstack?
Hello, if I would like to wipe, remove and purge everything devstack installed and configured what should I do? rm -rf /opt/stack rm -rf /usr/local/bin/ what else? thanks in advance! :) -- *guilherme* \n \t *maluf* ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] authentication failure for glance client in the latest devstack dev environment
I'm getting the same error! I tried to run devstack with a simple localrc but still happening the same error. stack@cloud-controller:~/devstack$ glance image-list Request returned failure status. Invalid OpenStack Identity credentials. On Fri, Nov 9, 2012 at 8:44 AM, Lu, Lianhao lianhao...@intel.com wrote: My system is Ubuntu 12.04 64bit. My nova list also failed with a HTTP 401 status error, with the following output on nova-api: 2012-11-09 18:30:09 ERROR keystone.common.cms [-] Verify error: Verification failure 139967656924832:error:04091077:rsa routines:INT_RSA_VERIFY:wrong signature length:rsa_sign.c:175: 139967656924832:error:2E09A09E:CMS routines:CMS_SignerInfo_verify_content:verification failure:cms_sd.c:900: 139967656924832:error:2E09D06D:CMS routines:CMS_verify:content verify error:cms_smime.c:425: 2012-11-09 18:30:09 WARNING keystone.middleware.auth_token [-] Authorization failed for token .. 2012-11-09 18:30:09 INFO keystone.middleware.auth_token [-] Invalid user token - rejecting request 2012-11-09 18:30:09 INFO nova.osapi_compute.wsgi.server [-] 10.239.36.61 GET /v2/447239d7ddfd4ae89393c9ecf538d703/servers/det ail HTTP/1.1 status: 401 len: 461 time: 0.0153220 However, the keystone command-line client works fine. Best Regards, Lianhao -Original Message- From: openstack-bounces+lianhao.lu=intel@lists.launchpad.net[mailto: openstack-bounces+lianhao.lu=intel@lists.launchpad.net] On Behalf Of Lu, Lianhao Sent: Friday, November 09, 2012 4:31 PM To: openstack@lists.launchpad.net; openstack-...@lists.openstack.org Subject: [Openstack] authentication failure for glance client in the latest devstack dev environment Hi fellows, Today I just updated my devstack to setup a new openstack dev environment with RECLONE set to yes in localrc. The stack.sh failed at the very end in glance image-create with the error of Invalid OpenStack Identify credential. I then tried to run glance image-list in the command line after source openrc admin, it also failed with the same error. When the error happens, glance-api server reported the following errors on the screen: 2012-11-09 16:20:31 16950 ERROR keystone.middleware.auth_token [-] HTTP connection exception: [Errno 1] _ssl.c:504: error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol 2012-11-09 16:20:31 16950 WARNING keystone.middleware.auth_token [-] Authorization failed for token MIIL7wYJKoZIhvcNAQcCoIIL4DCCC9wCAQExCTAHBgUrDgMCGjCCCkUGCSqGSIb3DQEHAaCCCjYEggoyeyJhY2Nlc3MiOiB7InRva2VuIjogeyJp c3N1ZWRfYXQiOiAiMDg6MjA6MzEuNjM3.(..omit here) A8uKBr1VlQoeF2Y-ND+DhZV+vjrM8i6FcGfeFq6Vra-1ktoQjkfh88XmG2tCcwrlGo0nVM4OrRaIs8F9Iwc4EIXHA+Aw73MzqUIRVSE8ahiFg9nNM = 2012-11-09 16:20:31 16950 INFO keystone.middleware.auth_token [-] Invalid user token - deferring reject downstream And the keystone reported the following: (eventlet.wsgi.server): 2012-11-09 16:28:21,276 DEBUG wsgi write 127.0.0.1 - - [09/Nov/2012 16:28:21] POST /v2.0/tokens HTTP/1.1 200 6780 0.095150 localhost - - [09/Nov/2012 16:28:21] code 400, message Bad request syntax (\x16\x03\x01\x00\xcd\x01\x00\x00\xc9\x03\x02P\x9c\xbe\xa5#\xc8D\xf8\xe9\xe9\x97\xc5w\x19LX\xfc\xb8\x04v\xb1w'\x04A\xa7}\xa8\x 0c) localhost - - [09/Nov/2012 16:28:21] ��P���#�DwLX�v�w'A�}� 400 - Does anyone know what's going wrong here? Yours, -Lianhao ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- *guilherme* \n \t *maluf* ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [devstack] Malformed Documentation on stack.sh script web site
thanks dean, looks beautiful now! :) On Wed, Nov 7, 2012 at 4:29 PM, Dean Troyer dtro...@gmail.com wrote: On Wed, Nov 7, 2012 at 9:27 AM, Gui Maluf guimal...@gmail.com wrote: In http://devstack.org/stack.sh.html above Log Files, the whole documentation is malformed. All descriptions stop to match with the current piece of code. I don't know who to warn, so I'm sending this email here. Actually, it is the reverse that is the case...everything _after_ Log Files is broken. We use shocco to format those pages from the bash scripts. It treats the comments as documentation and puts it to the left of the code that follows. This is why there is markdown formatting in the comments of devstack scripts. In this particular case, the spinner string was being improperly recognized by shocco and it stopped formatting the output. This is a good excuse to do another periodic doc/formatting pass through stack.sh, I'll commit this fix then. dt -- Dean Troyer dtro...@gmail.com -- *guilherme* \n \tab *maluf* ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] [devstack] Malformed Documentation on stack.sh script web site
In http://devstack.org/stack.sh.html above Log Files, the whole documentation is malformed. All descriptions stop to match with the current piece of code. I don't know who to warn, so I'm sending this email here. Hope it'll be fixed! att -- *guilherme* \n \tab *maluf* ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Using nova-volumes openstack LVM group for other pourposes
I think renaming the existent volume to a name that cinder/nova-volume recognize is enough. On Thu, Oct 25, 2012 at 8:48 AM, Daniel Vázquez daniel2d2...@gmail.com wrote: If we create a volume out of openstack context (it's is not created on nova database) only on system level. Can we after add to openstack? reformulate ask, Can we add to openstack an existen volumen (it's living on nova-volumes group)? I'm not sure on nova-volume create command or horizon ... that behavior it will be with existent lv label or some other properties. 2012/10/24 Daniel Vázquez daniel2d2...@gmail.com: Yeah!! Jon, I'm agree with you about organization/separation LVM groups, this is for very very very special situation. Any case if I use nova pattern labeling via logical volumen creation or via renaming label, I hope can switch the content of this custom logical volument to use with openstack, an attach to a VM in future. 2012/10/24 Jonathan Proulx j...@csail.mit.edu: On Wed, Oct 24, 2012 at 08:56:26PM +0200, Daniel Vázquez wrote: :Hi here! : :Can we create and use news logical volumes for own/custom use(out of :openstack) on nova-volumes openstack LVM group, and use it beside :openstack operational? :IMO it's LVM and no problem, but it has openstack collateral consequences? If you are talking about creating random logical volumes for non-openstack use in the same volume group nova-volume or cinder is using to create volumes (lv are in the same vg but don't otherwise interact), yes you can do that without ocnfusing openstack or having your volumes trampled. For example only having one volume group and using that for operating system partitions as well as volume-foo volumes for cinder I don't think it's a particularly good idea from an organizational standpoint I'd rather have distinct vg's for each purpose so it is clear which resources are operating system and which are data, but in my environment (a private computing/research cloud with a small admin group and 1k users in a few 10's of closely related tenents) it's probably more an aesthetic than technical choice. The larger and more diverse your situation the stronger I'd argue for keeping them in seperate VGs. -Jon ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- guilherme \n \tab maluf ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Additional iptables when two network interfaces
Did you enabled ip_forwarding? Try to use nova-api-metadata on node; When I tried to do the same set up I couldnt, my solution was using multi_host = true, starting nova-api-metadata on nodes. so each vm would get metadata info through it's own host and all traffic will go through this same host. My 0,1 cents, I hope you can fix it! On Tue, Oct 23, 2012 at 11:19 AM, Daniel Vázquez daniel2d2...@gmail.comwrote: Hi here!, Exists any additional iptables rules to add, when running on host with two network interfaces? Following documentation deduce that nova.conf has all info to mount all rules in live. I've problems to connect VMs instances, please can you review: https://answers.launchpad.net/nova/+question/212025 I can't see where is the problem. Thx! ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- *guilherme* \n \tab *maluf* ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] looking for a Nova scheduler filter plugin to boot nodes on named hosts
You may find what you want here: http://docs.openstack.org/trunk/openstack-compute/admin/content/ch_scheduling.html On Mon, Oct 15, 2012 at 8:45 PM, Christian Parpart tra...@gmail.com wrote: Hi all, I am looking for a (Essex) Nova scheduler plugin that parses the scheduler_hints to get a hostname of the hypervisor to spawn the actual VM on, rejecting any other node. This allows us to explicitely spawn a VM on a certain host (yes, there are really usecases where you want that). :-) I was trying to build my own and searching around since I couldn't believe I was the only one, but didn't find one yet. Does anyone of you maybe have the skills to actually write that simple plugin, or even maybe knows where such a plugin has already been developed? Many thanks in advance, Christian Parpart. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- *guilherme* \n \tab *maluf* ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Multi host nova-networking and local DNS resolving
I think it's true. Maybe you will have to setup some external dns if you want resolution between hosts. On Thu, Oct 4, 2012 at 4:51 AM, Doude doudou...@gmail.com wrote: Hi all, I saw this question : https://answers.launchpad.net/nova/+question/197603 Is it still true ? If yes, which workaround is possible ? Regards, Doude. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- *guilherme* \n \tab *maluf* ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] nova-manage service list does not list all nova services
You should give us /var/log/nova/{nova-api,nova-compute,nova-network}.log.
But please, use http://paste.openstack.org/, dont fill the email with logs
entry. Also paste /etc/nova/nova.conf and /etc/nova/api-paste.ini
Check the user and permissions of /etc/nova
and my last shot in the dark: flush the nova db and restart all services
$ mysql -uroot -p'MYSQLPASSWD' -e 'drop database nova;'
$ mysql -uroot -p'MYSQLPASSWD' -e 'create database nova;'
$ nova-manage db sync
$ for a in libvirt-bin nova-network nova-compute nova-api nova-objectstore
nova-scheduler nova-volume nova-consoleauth nova-cert; do service $a
restart; done
On Sat, Sep 29, 2012 at 7:56 AM, Ahmed Al-Mehdi ah...@coraid.com wrote:
Hi Trinath,
Thank you for your suggestion. Even though I am leery of reboot pc and
try again approach, I did give it a try.
After reboot (prior to starting any services, not even mysql), I
am seeing more odd behavior.
- Only nova-scheduler service is listed with an XXX status. I understand
why the XXX, but why is the other nova services not listed or for that
matter why is nova-scheduler list even though I have not started it?
root@sonoma root@sonoma:/etc:/etc root@sonoma:/etc# who -r
run-level 2 2012-09-29 02:57
root@sonoma root@sonoma:/etc:/etc root@sonoma:/etc# ls -l
/etc/rc2.d/*nova*
ls: cannot access /etc/rc2.d/*nova*: No such file or
directory
- After starting mysql, nova-scheduler is still listed with a XXX, but
now nova-consoleauth (which I did not start) is listed with a :), and no
other nova-services are not listed.
- After I start nova-scheduler, I see a :) for it.
- I started nova-api, and nova-network, but I don't see them listed.
root@sonoma:~# nova-manage service list
2012-09-29 02:57:30 DEBUG nova.utils [req-7fafe814-a2ba-4862-84b5
-e3eddaf838c8 None None] backend module 'nova.db.sqlalchemy.api' from
'/usr/lib/python2.7/dist-packages/nova/db/sqlalc
rom (pid=1742) __get_backend /usr/lib/python2.7
/dist-packages/nova/utils.py:658
2012-09-29 02:57:30 WARNING nova.db.sqlalchemy.session [req-7fafe814-a2ba
-4862-84b5-e3eddaf838c8 None None] SQL connection failed. 10 attempts
left.
Binary Host Zone
Status State Updated_At
nova-scheduler sonoma nova
enabledXXX 2012-09-29 09:54:09
root@sonoma:~# service mysql restart
mysql stop/waiting
mysql start/running, process 2372
root@sonoma:~
root@sonoma:~# nova-manage service list
2012-09-29 02:58:47 DEBUG
nova.utils[req-ad295ee2-ac50-41a0-bb75-636dbc8882c3None None]
backend module 'nova.db.sqlalchemy.api' from '/usr/lib/python2.7
/dist-packages/nova/db/sqlalc
rom (pid=2505) __get_backend /usr/lib/python2.7
/dist-packages/nova/utils.py:658
Binary Host Zone
Status State Updated_At
nova-scheduler sonoma nova
enabledXXX 2012-09-29 09:54:09
nova-consoleauth sonoma nova
enabled:-) 2012-09-29 09:58:44
root@sonoma:~# service nova-scheduler restart
stop: Unknown instance:
nova-scheduler start/running, process 2521
root@sonoma:~# nova-manage service list
2012-09-29 02:59:22 DEBUG
nova.utils[req-e88c4d94-fc28-4bab-b49d-fc99601f75ceNone None]
backend module 'nova.db.sqlalchemy.api' from '/usr/lib/python2.7
/dist-packages/nova/db/sqlalc
rom (pid=2538) __get_backend /usr/lib/python2.7
/dist-packages/nova/utils.py:658
Binary Host Zone
Status State Updated_At
nova-scheduler sonoma nova
enabled:-) 2012-09-29 09:59:18
nova-consoleauth sonoma nova
enabled:-) 2012-09-29 09:59:14
root@sonoma:~# service nova-api start
start: Job is already running: nova-api
root@sonoma:~# nova-manage service list
2012-09-29 02:59:42 DEBUG
nova.utils[req-fc7d7908-75bd-4b8e-ae5b-6edc72df1ec3None None]
backend module 'nova.db.sqlalchemy.api' from '/usr/lib/python2.7
/dist-packages/nova/db/sqlalc
rom (pid=2547) __get_backend /usr/lib/python2.7
/dist-packages/nova/utils.py:658
Binary Host Zone
Status State Updated_At
nova-scheduler sonoma nova
enabled:-) 2012-09-29 09:59:38
nova-consoleauth sonoma nova
enabled:-) 2012-09-29 09:59:35
root@sonoma root@sonoma:/etc:/etc root@sonoma:/etc# service
nova-network start
nova-network start/running, process 3550
root@sonoma root@sonoma:/etc:/etc root@sonoma:/etc#
root@sonoma root@sonoma:/etc:/etc root@sonoma:/etc# nova-manage
service list
2012-09-29 03:45:03 DEBUG
nova.utils[req-fa150ddb-1c24-4bca-8b4f-351130abf76bNone None]
backend module 'nova.db.sqlalchemy.api' from '/usr/lib/pyt
rom (pid=3576) __get_backend /usr/lib/python2.7
/dist-packages/nova/utils.py:658
Binary
Re: [Openstack] Can't ping vm to google
Jon, I was facing a similar problem, the only difference was I had 2 NICs. I've tried many things to figure out what was happening, but I found nothing. What I did to fix it was use multi_host[https://lists.launchpad.net/openstack/msg16656.html] set up, then all vms was able to access internet. I think a important information is the iptables NAT table. And I workaround that may be usefull is kill dnsmasq, as restart nova services. I would like to know more about why this is happening. Why vms can resolve name but can't receive the packets back, is a iptable issue? a route issue? masquerade, or what? hope you can fix it On Thu, Sep 27, 2012 at 3:08 PM, Jon Thomas jtho...@redhat.com wrote: Hi, I have a control node running nova-network using FlatDHCPManager and a compute node only running nova-compute. It's a single nic setup. I can start VM's on the compute node and ssh/ping them from the control node. I can also ping from vm to control node bridge ip and em1 device ip. However, I cannot ping from the VM to outside internet ( although DNS apparently works). I set em1 on both to promisc and have ip-forwarding on. iptables seem to have the right entries. Any ideas? here's conf, iptables, etc: http://paste.openstack.org/show/21159/ thx ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- guilherme \n \tab maluf ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Setup described in OpenStack Install and Deploy Manual - Ubuntu
I think in OpenStack, services may run in different servers, so there is no correct setup. What the manual say about network config is: This walkthrough shows network configurations for a single server. For OpenStack Compute, networking is configured on multi-node installations between the physical machines on a single subnet. Anyway you can use both setup's through the manual, once it divide the installation in two things: controller and node. You can mix both together, making the node installation inside the controller, OR you can put node-compute and controller in complete separated servers. On Fri, Sep 28, 2012 at 4:34 AM, Ahmed Al-Mehdi ah...@coraid.com wrote: Hello, I am following the steps mentioned in the OpenStack Install and Deploy Manual - Ubuntu (http://docs.openstack.org/trunk/openstack-compute/install/apt/content/). I am a bit confused about how the setup (which server performs which function). This confusion arose after looking at the Network section of nova.conf (Page 47). Which of the following best describes the setup in the manual: Setup1: Physical server1 - controller node and compute node. User can setup additional compute node(s). Setup2: Physical server1- controller node. Physical server2 - computer node. User can setup additional compute node(s). If Setup1 is the answer, then why does the /etc/network/interfaces file (mentioned in section Pre-configuring the network on Page 44), does not mention the static IP address of eth0 - 192.168.206.130. eth0 is the public interface but is use to the private network as well, so it should get the ip address via dhcp, and have access to Internet with this iface. With controller+node on the same server, nova-network will use eth0 as a bridge for all vm's and to provide outside access to Internet for vms and server. There isn't need to mention the ip address of eth0, Once the static or dhcp configuration will depends on your whole network/LAN set up. ip address of eth0 will vary on your config, but I'm pretty sure is suppose to be a fixed IP address. If Setup2 is the answer, then what is the use of some of the entries in the network section of nova.conf file on the controller node (pertaining to bridge and IP address range) mentioned in Page 47): public_interface=br100 vlan_interface=eth0 flat_network_bridge=br100 flat_interface=eth0 fixed_range=10.0.0.0/24 I think nova.conf is meant to be the same for all node. In setup1 or setup2 this configuration will be use once the eth0 is the only interface available for both compute and controller. Both will use eth0 to have access to private and public network. I don't know if I was able to answer your question. If I'm was not clear I hope some one can help you. Thank you very much in advance. My apologies if this is a newbie question, as I am just learning to use the OpenStack platform. I am happy to repost my message to the appropriate mailing list (doc related) if this is not the correct one. Regards, Ahmed. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- guilherme \n \tab maluf ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Please provide the step by step guide for 3 node swift instalation steps
it's well documented here: http://docs.openstack.org/essex/openstack-compute/install/apt/openstack-install-guide-essex.pdf On Tue, Sep 18, 2012 at 3:52 AM, John Raja john.r...@indiainfoline.com wrote: Please provide the step by step guide for 3 node swift instalation steps . Regards, John Raja Ip Extn :- 509028 Tel:- 022-40609028 ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- guilherme \n \tab maluf Dominar-se a si próprio é uma vitória maior do que vencer a milhares em uma batalha. Sakyamuni ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [Horizon-Q] Horizon in Essex does not support multi Availability Zones?
have you checked on /etc/openstack-dashboard/local_settings.py ?
maybe this lines will help you
# For multiple regions uncomment this configuration, and add (endpoint, title).
# AVAILABLE_REGIONS = [
# ('http://cluster1.example.com:5000/v2.0', 'cluster1'),
# ('http://cluster2.example.com:5000/v2.0', 'cluster2'),
# ]
On Fri, Sep 14, 2012 at 4:26 PM, Sean Bigdatafun
sean.bigdata...@gmail.com wrote:
Hi OpenStackers,
I am trying to setup a cluster with two availability-zones because of my
hardware setup, one called 'nova' and the other called 'high'.
It looks Essex does support this, however, the Horizon does not. In other
words, I seem to be able to create a VM in a specified availability zone
'high' in CLI, but not able to do so in Horizon dashboard.
Plus, it looks that Horizon is not able to display the availability zone
information at all? Have I missed something here?
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
--
guilherme \n
\tab maluf
Dominar-se a si próprio é uma vitória maior do que vencer a milhares
em uma batalha. Sakyamuni
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Error in Horizon or misconfiguration?
Are you using keystone catalog ? check if api-paste keystone configs
are correct.
check if nova-api is running. check if endpoint is correctly created
with # keystone endpoint-list
I don't have any other clue. :/
On Tue, Sep 18, 2012 at 9:21 AM, Matthias Runge
mru...@matthias-runge.de wrote:
Hi,
currently, I'm testing horizon-rc1.
I'm logged in as admin, and click on any link in the project tab, e.g. on
Overview calling the url http://localhost/dashboard/nova/
Then I'm getting an error in http-error-log:
[Tue Sep 18 12:16:37 2012] [error] unable to retrieve service catalog with
token
[Tue Sep 18 12:16:37 2012] [error] Traceback (most recent call last):
[Tue Sep 18 12:16:37 2012] [error] File
/usr/lib/python2.7/site-packages/keystoneclient/v2_0/client.py, line 132,
in _extract_service_catalog
[Tue Sep 18 12:16:37 2012] [error] endpoint_type='adminURL')
[Tue Sep 18 12:16:37 2012] [error] File
/usr/lib/python2.7/site-packages/keystoneclient/service_catalog.py, line
62, in url_for
[Tue Sep 18 12:16:37 2012] [error] raise
exceptions.EndpointNotFound('Endpoint not found.')
[Tue Sep 18 12:16:37 2012] [error] EndpointNotFound: Endpoint not found.
By chance, has anybody a clue, what went wrong or how to debug this further?
There's no error in keystones logs. Keystone answers and does not report an
error.
Thanks,
Matthias
--
Matthias Runge mru...@matthias-runge.de
mru...@fedoraproject.org
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
--
guilherme \n
\tab maluf
Dominar-se a si próprio é uma vitória maior do que vencer a milhares
em uma batalha. Sakyamuni
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Private instances can't access Internet
I'm facing the same problem and I can't solve it! Please, someone help us! Instances from cc-node can reach Internet, but the node instances can't! CC-node configs: http://paste.openstack.org/show/20861/ Node configs: http://paste.openstack.org/show/20862/ ps: i'm not using multi_host I've tried many things, but I can't make my instance on node reach internet. Dave Pigott Mon, 10 Sep 2012 03:09:34 -0700 Hi Jason, Try setting --multi_host in nova.conf Dave Sent from my Aldis Lamp On 7 Sep 2012, at 20:50, Jason Cooper ja...@presdo.com wrote: Hi Everyone. I just completed the steps in the OpenStack Compute Starter Guide to get OpenStack up and running on my server, and everything is working wonderfully except that my private instances cannot access the public Internet. I have configured the physical server on which OpenStack is running to access the public Internet over eth0. I have also set up an internal network on eth1 with a bridge so the instances, which all have fixed private IP addresses (e.g. 192.168.4.x) should be able to ping the public Internet through this bridge. However, this isn't working, and I'm hoping you can help explain what I'm doing wrong. I have already tried to setup IP forwarding by following the instructions at https://lists.launchpad.net/openstack/msg15559.html, but this did not help. Here is my /etc/network/interfaces: # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto eth0 iface eth0 inet static address 10.0.1.130 netmask 255.255.0.0 broadcast 10.0.1.255 gateway 10.0.0.1 dns-nameservers 8.8.8.8 auto eth1 iface eth1 inet static address 192.168.3.1 netmask 255.255.255.0 network 192.168.3.0 broadcast 192.168.3.255 And here is my /etc/nova/nova.conf: --dhcpbridge_flagfile=/etc/nova/nova.conf --dhcpbridge=/usr/bin/nova-dhcpbridge --logdir=/var/log/nova --state_path=/var/lib/nova --lock_path=/var/lock/nova --allow_admin_api=true --use_deprecated_auth=false --auth_strategy=keystone --scheduler_driver=nova.scheduler.simple.SimpleScheduler --s3_host=10.0.1.130 --ec2_host=10.0.1.130 --rabbit_host=10.0.1.130 --cc_host=10.0.1.130 --nova_url=http://10.0.1.130:8774/v1.1/ --routing_source_ip=10.0.1.130 --glance_api_servers=10.0.1.130:9292 --image_service=nova.image.glance.GlanceImageService --iscsi_ip_prefix=192.168.4 --sql_connection=mysql://novadbadmin:novasecret@10.0.1.130/nova --ec2_url=http://10.0.1.130:8773/services/Cloud --keystone_ec2_url=http://10.0.1.130:5000/v2.0/ec2tokens --api_paste_config=/etc/nova/api-paste.ini --libvirt_type=kvm --libvirt_use_virtio_for_bridges=true --start_guests_on_host_boot=true --resume_guests_state_on_host_boot=true # vnc specific configuration --novnc_enabled=true --novncproxy_base_url=http://10.0.1.130:6080/vnc_auto.html --vncserver_proxyclient_address=10.0.1.130 --vncserver_listen=10.0.1.130 # network specific settings --network_manager=nova.network.manager.FlatDHCPManager --public_interface=eth0 --flat_interface=eth1 --flat_network_bridge=br100 --fixed_range=192.168.4.1/27 #--floating_range=10.10.10.2/27 --network_size=32 --flat_network_dhcp_start=192.168.4.33 --flat_injected=False --force_dhcp_release --iscsi_helper=tgtadm --connection_type=libvirt --root_helper=sudo nova-rootwrap --verbose Lastly, here is the command I used to create the network: sudo nova-manage network create private --fixed_range_v4=192.168.4.32/27 --num_networks=1 --bridge=br100 --bridge_interface=eth1 --network_size=32 You can see that I'm not using a floating IP range. My instances are able to access the public Internet if I change my configuration to use a floating range, but I prefer to find a solution that allows me to assign an internal IP to my instances and use the specified bridge to contact the outside world. Any help is appreciated, and many thanks in advance. - Jason ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- guilherme \n \tab maluf Dominar-se a si próprio é uma vitória maior do que vencer a milhares em uma batalha. Sakyamuni ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Private instances can't access Internet
My node and my CC are connected through a switch, both has access to Internet. I've tried to use multi_host, but with no success. I'm trying again to set up with multi_host, since makes more sense in my network setup. After I set up multi_host=true and enabled_apis=ec2,osapi_compute,osapi_volume,metadata my node is working but my cc-node stop to work, instances running on my cc-node can't get the right route table(192.x.x.x rather then 10.x.x.x) and can't reach metadata server(this is the same issue I faced using multi_host). On Tue, Sep 11, 2012 at 3:04 PM, Ritesh Nanda riteshnand...@gmail.com wrote: Hello Gui, your Config file shows you are using --multi-host. In case you don't use multi-host all traffic would leave to Internet from the controller node. Just in case how is your two node connected , are they connected directly or using a switch. On Tue, Sep 11, 2012 at 11:01 PM, Gui Maluf guimal...@gmail.com wrote: I'm facing the same problem and I can't solve it! Please, someone help us! Instances from cc-node can reach Internet, but the node instances can't! CC-node configs: http://paste.openstack.org/show/20861/ Node configs: http://paste.openstack.org/show/20862/ ps: i'm not using multi_host I've tried many things, but I can't make my instance on node reach internet. Dave Pigott Mon, 10 Sep 2012 03:09:34 -0700 Hi Jason, Try setting --multi_host in nova.conf Dave Sent from my Aldis Lamp On 7 Sep 2012, at 20:50, Jason Cooper ja...@presdo.com wrote: Hi Everyone. I just completed the steps in the OpenStack Compute Starter Guide to get OpenStack up and running on my server, and everything is working wonderfully except that my private instances cannot access the public Internet. I have configured the physical server on which OpenStack is running to access the public Internet over eth0. I have also set up an internal network on eth1 with a bridge so the instances, which all have fixed private IP addresses (e.g. 192.168.4.x) should be able to ping the public Internet through this bridge. However, this isn't working, and I'm hoping you can help explain what I'm doing wrong. I have already tried to setup IP forwarding by following the instructions at https://lists.launchpad.net/openstack/msg15559.html, but this did not help. Here is my /etc/network/interfaces: # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto eth0 iface eth0 inet static address 10.0.1.130 netmask 255.255.0.0 broadcast 10.0.1.255 gateway 10.0.0.1 dns-nameservers 8.8.8.8 auto eth1 iface eth1 inet static address 192.168.3.1 netmask 255.255.255.0 network 192.168.3.0 broadcast 192.168.3.255 And here is my /etc/nova/nova.conf: --dhcpbridge_flagfile=/etc/nova/nova.conf --dhcpbridge=/usr/bin/nova-dhcpbridge --logdir=/var/log/nova --state_path=/var/lib/nova --lock_path=/var/lock/nova --allow_admin_api=true --use_deprecated_auth=false --auth_strategy=keystone --scheduler_driver=nova.scheduler.simple.SimpleScheduler --s3_host=10.0.1.130 --ec2_host=10.0.1.130 --rabbit_host=10.0.1.130 --cc_host=10.0.1.130 --nova_url=http://10.0.1.130:8774/v1.1/ --routing_source_ip=10.0.1.130 --glance_api_servers=10.0.1.130:9292 --image_service=nova.image.glance.GlanceImageService --iscsi_ip_prefix=192.168.4 --sql_connection=mysql://novadbadmin:novasecret@10.0.1.130/nova --ec2_url=http://10.0.1.130:8773/services/Cloud --keystone_ec2_url=http://10.0.1.130:5000/v2.0/ec2tokens --api_paste_config=/etc/nova/api-paste.ini --libvirt_type=kvm --libvirt_use_virtio_for_bridges=true --start_guests_on_host_boot=true --resume_guests_state_on_host_boot=true # vnc specific configuration --novnc_enabled=true --novncproxy_base_url=http://10.0.1.130:6080/vnc_auto.html --vncserver_proxyclient_address=10.0.1.130 --vncserver_listen=10.0.1.130 # network specific settings --network_manager=nova.network.manager.FlatDHCPManager --public_interface=eth0 --flat_interface=eth1 --flat_network_bridge=br100 --fixed_range=192.168.4.1/27 #--floating_range=10.10.10.2/27 --network_size=32 --flat_network_dhcp_start=192.168.4.33 --flat_injected=False --force_dhcp_release --iscsi_helper=tgtadm --connection_type=libvirt --root_helper=sudo nova-rootwrap --verbose Lastly, here is the command I used to create the network: sudo nova-manage network create private --fixed_range_v4=192.168.4.32/27 --num_networks=1 --bridge=br100 --bridge_interface=eth1 --network_size=32 You can see that I'm not using a floating IP range. My instances are able to access the public Internet if I change my configuration to use a floating range, but I prefer to find a solution that allows me to assign an internal IP to my instances and use the specified bridge to contact the outside world. Any help
Re: [Openstack] Private instances can't access Internet
As I said, now I'm trying to put multi_host working.
Now, this is my situation:
Instances running on node(nova-{network,compute,volume}) can reach
Internet, reach metadata server and get correct route table (ip addr
10.5.5.33), I can even ping from outside the LAN(using cc-node as
gateway to 10.5.5.0 network)
Instances running on cc-node(nova-* + other services) can't reach
Internet, can't reach metadata server cause they get the route table
with IP addr 192.168.1.33 (libvirt network??). I can't ping neither
inside or outside the lan.
The difference from the files I pasted is:
Node:
--my_ip=150.164.3.240
--multi_host=true
--enabled_apis=ec2,osapi_compute,osapi_volume,metadata
--routing_source_ip=150.164.3.240
CC:
--my_ip=150.164.3.239
--multi_host=true
--routing_source_ip=150.164.3.239
Creating network with: nova-manage network create private
--fixed_range_v4=10.5.5.32/27 --num_networks=1 --bridge=br100
--bridge_interface=eth1 --network_size=32
If I create the network(nova-manage network create) with
--multi_host=T, node and cc-node can't reach metadata server cause
both get 192.168.1.X gateway or the public ip gateway(150.164.x.x).
If I put --enabled_apis=ec2,osapi_compute,osapi_volume,metadata on
cc-node, the same problem above happens.
I'm really confuse, and spending a lot of time to put network working.
I would really appreciate if someone could help;
If I'd miss some information, please let me know!
Thanks
On Tue, Sep 11, 2012 at 3:43 PM, Gui Maluf guimal...@gmail.com wrote:
My node and my CC are connected through a switch, both has access to
Internet. I've tried to use multi_host, but with no success. I'm
trying again to set up with multi_host, since makes more sense in my
network setup.
After I set up multi_host=true and
enabled_apis=ec2,osapi_compute,osapi_volume,metadata my node is
working but my cc-node stop to work, instances running on my cc-node
can't get the right route table(192.x.x.x rather then 10.x.x.x) and
can't reach metadata server(this is the same issue I faced using
multi_host).
On Tue, Sep 11, 2012 at 3:04 PM, Ritesh Nanda riteshnand...@gmail.com wrote:
Hello Gui,
your Config file shows you are using --multi-host.
In case you don't use multi-host all traffic would leave to Internet from
the controller node.
Just in case how is your two node connected , are they connected directly
or using a switch.
On Tue, Sep 11, 2012 at 11:01 PM, Gui Maluf guimal...@gmail.com wrote:
I'm facing the same problem and I can't solve it!
Please, someone help us!
Instances from cc-node can reach Internet, but the node instances can't!
CC-node configs: http://paste.openstack.org/show/20861/
Node configs: http://paste.openstack.org/show/20862/
ps: i'm not using multi_host
I've tried many things, but I can't make my instance on node reach
internet.
Dave Pigott
Mon, 10 Sep 2012 03:09:34 -0700
Hi Jason,
Try setting --multi_host in nova.conf
Dave
Sent from my Aldis Lamp
On 7 Sep 2012, at 20:50, Jason Cooper ja...@presdo.com wrote:
Hi Everyone. I just completed the steps in the OpenStack Compute
Starter
Guide to get OpenStack up and running on my server, and everything is
working
wonderfully except that my private instances cannot access the public
Internet.
I have configured the physical server on which OpenStack is running to
access
the public Internet over eth0. I have also set up an internal network
on eth1
with a bridge so the instances, which all have fixed private IP
addresses
(e.g. 192.168.4.x) should be able to ping the public Internet through
this
bridge. However, this isn't working, and I'm hoping you can help
explain what
I'm doing wrong.
I have already tried to setup IP forwarding by following the
instructions at
https://lists.launchpad.net/openstack/msg15559.html, but this did not
help.
Here is my /etc/network/interfaces:
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
auto eth0
iface eth0 inet static
address 10.0.1.130
netmask 255.255.0.0
broadcast 10.0.1.255
gateway 10.0.0.1
dns-nameservers 8.8.8.8
auto eth1
iface eth1 inet static
address 192.168.3.1
netmask 255.255.255.0
network 192.168.3.0
broadcast 192.168.3.255
And here is my /etc/nova/nova.conf:
--dhcpbridge_flagfile=/etc/nova/nova.conf
--dhcpbridge=/usr/bin/nova-dhcpbridge
--logdir=/var/log/nova
--state_path=/var/lib/nova
--lock_path=/var/lock/nova
--allow_admin_api=true
--use_deprecated_auth=false
--auth_strategy=keystone
--scheduler_driver=nova.scheduler.simple.SimpleScheduler
--s3_host=10.0.1.130
--ec2_host=10.0.1.130
--rabbit_host=10.0.1.130
--cc_host=10.0.1.130
--nova_url=http://10.0.1.130:8774/v1.1/
--routing_source_ip=10.0.1.130
--glance_api_servers=10.0.1.130:9292
--image_service=nova.image.glance.GlanceImageService
--iscsi_ip_prefix=192.168.4
--sql_connection=mysql
