Re: [openstack-dev] iso8601 filling up nova logs
+1 - looks like this is where you need to add it [1], if so, the
change needs to be in oslo-incubator repo first [2], so please submit
a review there
[1]
https://github.com/openstack/nova/blob/master/nova/openstack/common/log.py#L128
[2]
https://github.com/openstack/oslo-incubator/blob/master/openstack/common/log.py#L130
On Thu, Nov 7, 2013 at 3:45 PM, Tracy Jones tjo...@vmware.com wrote:
My nova logs are full of this - is it ok if I make a change to the default
log level to set iso8601 to WARN?
2:39:54.683 DEBUG iso8601.iso8601 [-] Parsed 2013-11-06T06:38:00Z into
{'tz_sign': None, 'second_fraction': None, 'hour': u'06', 'tz_hour': None,
'month': u'11', 'timezone': u'Z', 'second': u'00', 'tz_minute': None,
'year': u'2013', 'separator': u'T', 'day': u'06', 'minute': u'38'} with
default timezone iso8601.iso8601.Utc object at 0x2adcc90 from (pid=14941)
parse_date /usr/local/lib/python2.7/dist-packages/iso8601/iso8601.py:166
2013-11-05 22:39:54.684 DEBUG iso8601.iso8601 [-] Got u'2013' for 'year'
with default None from (pid=14941) to_int
/usr/local/lib/python2.7/dist-packages/iso8601/iso8601.py:124
2013-11-05 22:39:54.684 DEBUG iso8601.iso8601 [-] Got u'11' for 'month' with
default None from (pid=14941) to_int
/usr/local/lib/python2.7/dist-packages/iso8601/iso8601.py:124
2013-11-05 22:39:54.684 DEBUG iso8601.iso8601 [-] Got u'06' for 'day' with
default None from (pid=14941) to_int
/usr/local/lib/python2.7/dist-packages/iso8601/iso8601.py:124
2013-11-05 22:39:54.685 DEBUG iso8601.iso8601 [-] Got u'06' for 'hour' with
default None from (pid=14941) to_int
/usr/local/lib/python2.7/dist-packages/iso8601/iso8601.py:124
2013-11-05 22:39:54.685 DEBUG iso8601.iso8601 [-] Got u'38' for 'minute'
with default None from (pid=14941) to_int
/usr/local/lib/python2.7/dist-packages/iso8601/iso8601.py:124
2013-11-05 22:39:54.685 DEBUG iso8601.iso8601 [-] Got u'00' for 'second'
with default None from (pid=14941) to_int
/usr/local/lib/python2.7/dist-packages/iso8601/iso8601.py:124
2013-11-05 22:39:54.686 DEBUG iso8601.iso8601 [-] Parsed 2013-11-0
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Davanum Srinivas :: http://davanum.wordpress.com
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Openstack] [Neutron] Security groups issue when running latest libvirt?
Le 07/11/2013 03:18, Martinx - ジェームズ a écrit :
That is true... Back to LibvirtHybridOVSBridgeDriver, Security Groups
is working again...
Thanks for the feedback Thiago. I've opened a bug on Launchpad:
https://bugs.launchpad.net/nova/+bug/1248859
On 6 November 2013 15:03, Simon Pasquier simon.pasqu...@bull.net
mailto:simon.pasqu...@bull.net wrote:
Answering myself as I investigated a little further and
cross-posting to openstack-dev because I'd like to get feedback from
Nova/Neutron devs.
Users running Havana should configure
libvirt_vif_driver=nova.virt.__libvirt.vif.__LibvirtHybridOVSBridgeDriver.
This driver is still available in the Havana release although
deprecated. AFAIU, this is the only option if you want effective
security groups with KVM OVS.
For people using the master branch of nova, sorry but security
groups are currently broken because LibvirtHybridOVSBridgeDriver is
gone ([0]). Joe Gordon asked the Neutron devs about it few weeks ago
[1] but no answer and in another review [2], the conclusion was that
the Tempest tests passed with Neutron. However I don't see anywhere
in the tests ([3], [4]) that we check if the security rules
allow/block traffic.
It would be nice if core devs could confirm or refute.
Regards,
Simon
[0] https://review.openstack.org/#__/c/49660/
https://review.openstack.org/#/c/49660/
[1]
http://lists.openstack.org/__pipermail/openstack-dev/2013-__October/016886.html
http://lists.openstack.org/pipermail/openstack-dev/2013-October/016886.html
[2] https://review.openstack.org/#__/c/44349
https://review.openstack.org/#/c/44349
[3]
https://github.com/openstack/__tempest/blob/master/tempest/__api/network/test_security___groups.py
https://github.com/openstack/tempest/blob/master/tempest/api/network/test_security_groups.py
[4]
https://github.com/openstack/__tempest/blob/master/tempest/__api/network/test_security___groups_negative.py
https://github.com/openstack/tempest/blob/master/tempest/api/network/test_security_groups_negative.py
Le 05/11/2013 14:57, Simon Pasquier a écrit :
Hi all,
I'm struggling with security groups on Havana with Neutron and OVS
plugin (GRE tunnels). No problem to create/delete security group
rules
but even though iptables configuration is updated, traffic to my
instances is never filtered [0].
I'm running DevStack on 2 nodes (1 controller + 1 compute):
- OS: Ubuntu 12.04.3 (LTS) with the Havana cloud archive repository.
- Open vSwitch package version: 1.10.2-0ubuntu2~cloud0
- libvirt package version: 1.1.1-0ubuntu8~cloud2
- localrc, nova.conf, neutron.conf and ovs_neutron_plugin.ini files
pasted at [1] (I didn't modify any of these files after the
DevStack run)
According to [2], [3] and [4], iptables is not compatible with TAP
devices connectd directly to Open vSwitch ports, this is why
there used
to be the additional veth + bridge interfaces [5]. But in my
setup, this
is not the case anymore as shown in [6] ('ovs-vsctl show' +
'iptables-save' ouptut). I've also pasted the libvirt XML
configuration
[7] that shows that the instance is directly connected to the
Open vSwitch.
Are the security groups supposed to work when the instance is
directly
connected to OVS? If yes, what am I doing wrong?
Regards,
[0] http://paste.openstack.org/__show/50490/
http://paste.openstack.org/show/50490/
[1] http://paste.openstack.org/__show/50448/
http://paste.openstack.org/show/50448/
[2]
http://www.spinics.net/linux/__fedora/libvirt-users/msg05384.__html
http://www.spinics.net/linux/fedora/libvirt-users/msg05384.html
[3]
http://openvswitch.org/__pipermail/discuss/2013-__October/011461.html
http://openvswitch.org/pipermail/discuss/2013-October/011461.html
[4]
http://docs.openstack.org/__havana/config-reference/__content/under_the_hood___openvswitch.html
http://docs.openstack.org/havana/config-reference/content/under_the_hood_openvswitch.html
[5]
http://docs.openstack.org/__havana/config-reference/__content/figures/7/a/a/common/__figures/under-the-hood-__scenario-2-ovs-compute.png
http://docs.openstack.org/havana/config-reference/content/figures/7/a/a/common/figures/under-the-hood-scenario-2-ovs-compute.png
[6] http://paste.openstack.org/__show/50486/
http://paste.openstack.org/show/50486/
[7] http://paste.openstack.org/__show/50487/
http://paste.openstack.org/show/50487/
--
Simon Pasquier
Software Engineer
Bull, Architect of an Open World
Phone: + 33 4 76 29 71 49 tel:%2B%2033%204%2076%2029%2071%2049
http://www.bull.com
[openstack-dev] [Heat] How do i implement this usecase:
Currently my heat template works with AWS resource type:
DatabaseIPAddress:
Type: AWS::EC2::EIP
DatabaseIPAssoc :
Type: AWS::EC2::EIPAssociation
Properties:
InstanceId: {Ref: BaseInstance}
EIP: {Ref: MyIPAddress}
Now if i want to change to OpenStack ( OS ) namespace with a similar
implementation :
MyIPAddress:
Type: OS::Neutron::FloatingIP
Properties:
floating_network_id : String
MyIPAssoc :
Type: OS::Neutron::FloatingIPAssociation
Properties:
floatingip_id : {Ref: MyIPAddress}
I cannot problem is,
a) floating_network_id ( is not known ) which is a required property.
b) Even if its available / defaults to, its an overhead from AWS simplicity.
--
Consultant Engineering
Team: HPCS-Vertica
Location: Noida, India
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Bad review patterns
On 06/11/13 23:07, Robert Collins wrote: On 6 November 2013 21:34, Radomir Dopieralski openst...@sheep.art.pl wrote: [...] Firstly, things like code duplication is a sliding scale, and I think it's ok for a reviewer to say 'these look similar, give it a go please'. If the reviewee tries, and it's no good - thats fine. But saying 'hey, I won't even try' - thats not so good. Many times we get drive-by patches and no follow up, so there is a learnt response to require full satisfaction with each patch that comes in. Regular contributors get more leeway here I think. This is of course a gut feeling thing, and different people have different thresholds for when to deduplicate code. I came up with that pattern for myself, because my feelings about the code often didn't match the feelings of the rest of the team. Please note that the fact that I notice a bad pattern in my review doesn't immediately mean I shouldn't do it -- just that it is suspect and I should rethink it. So, if it's a blatant copy-paste of code, of course I will point it out. If the patch includes code that could be easily replaced by an existing utility function, that the author might not know about, of course I will point it out. But if the code is similar to some other code in some other part of the project, I will try to treat it the same way as when I spot a bug that is not related to the patch during the review -- either follow up with a patch of my own, or report a bug if I don't have time for this (this has a nice side effect of producing the low-hanging-fruit bugs that teach refactoring to newcomers). I think it's important to remember that you can always commit to that project, so not all changes need to be mde by that single author (especially in OpenStack, where you have the marvelous option of amending someone else's patch). [...] This is quite obvious. Just don't do it. It's OK to spend an hour reviewing something, and then leaving no comments on it, because it's simply fine, or because we had to means to test someting (see the first pattern). Core reviewers look for the /comments/ from people, not just the votes. A +1 from someone that isn't core is meaningless unless they are known to be a thoughtful code reviewer. A -1 with no comment is also bad, because it doesn't help the reviewee get whatever the issue is fixed. It's very much not OK to spend an hour reviewing something and then +1 with no comment: if I, and I think any +2er across the project see a patch that needs an hour of review, with a commentless +1, we'll likely discount the +1 as being meaningful. That is a very good point! We want reviews that have useful comments in them, so it is indeed a very good rule of thumb to always ask yourself Is this comment that I am posting helpful?. What I meant here is that if I do a review, and even after spending a lot of time on it, can't come up with anything that would actually help the author make it a better patch, then it is fine to not post anything at all, including no score. I suppose it would be nice to +1 it if you find it basically fine, but we didn't have separate +1s and +2s in my previous project. -- Radomir Dopieralski ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] How to choose proper availablity-zone in Havana version with the same usage realized by JsonFilter in Folsom version?
Hi guys, In Folsom version, availability-zone info is stored in compute_nodes db table, and so can be parsed by JsonFilter. I can use JsonFilter to choose which(or except which) availability-zones to build my instance. But in Havana version, availability-zone info is stored in aggregatemetadata, and so JsonFilter seems can not filter the proper availatiliby-zones as the way in Folsom version. So Is there any other existed resolution in H version that can satisfy my demand? Thanks~ -- Best regards! GuanQiang 2013-11-07___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Bad review patterns
On 11/07/2013 08:25 AM, Daniel P. Berrange wrote: On Thu, Nov 07, 2013 at 12:21:38AM +, Day, Phil wrote: Leaving a mark. === You review a change and see that it is mostly fine, but you feel that since you did so much work reviewing it, you should at least find *something* wrong. So you find some nitpick and -1 the change just so that they know you reviewed it. This is quite obvious. Just don't do it. It's OK to spend an hour reviewing something, and then leaving no comments on it, because it's simply fine, or because we had to means to test someting (see the first pattern). Another one that comes into this category is adding a -1 which just says I agree with the other -1's in here. If you have some additional perspective and can expand on it then that's fine - otherwise it adds very little and is just review count chasing. I don't think that it is valueless as you describe. If I multiple people add '-1' with a same comments as name, then as a core reviewer I will consider that initial -1 to be a much stronger nack, than if only one person had added the -1. So I welcome people adding I agree with blah to any review. It's an unfortunate consequence of counting and publishing review stats that having such a measure will inevitable also drive behavour. IMHO what this shows is not people trying to game the stats, but rather the inadequacy of gerrit. We don't have any way to distinguish a -1 minor nice to have nitpick from a -1 serious code issue that is a must-fix. Adding a -2 is really too heavyweight because it is sticky, and implies do not ever merge this. It would be nice to be able to use '-2' for serious must-fix issue without it being sticky, and have a separate way for core reviewers to put an review into a block from being merged indefinitely state - perhaps a new state would be more useful eg a Blocked state, to add to New, Open, Merged, Abadoned. Daniel The comment describing the -1 should be enough to distinquish between minor nitpick and serious code issue IMHO. If it is a serious issue, other reviewers also giving -1 confirming the issue is probably a good thing. (Not with the minor nit though...) Jirka ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Heat] How do i implement this usecase:
SnowDust, hi, are there any needs of Neutron usage(in trove)? Since nova
supports nova-network i suppose we could keep networking with nova.
2013/11/7 Nilakhya nilakhya.chatter...@globallogic.com
Currently my heat template works with AWS resource type:
DatabaseIPAddress:
Type: AWS::EC2::EIP
DatabaseIPAssoc :
Type: AWS::EC2::EIPAssociation
Properties:
InstanceId: {Ref: BaseInstance}
EIP: {Ref: MyIPAddress}
Now if i want to change to OpenStack ( OS ) namespace with a similar
implementation :
MyIPAddress:
Type: OS::Neutron::FloatingIP
Properties:
floating_network_id : String
MyIPAssoc :
Type: OS::Neutron::FloatingIPAssociation
Properties:
floatingip_id : {Ref: MyIPAddress}
I cannot problem is,
a) floating_network_id ( is not known ) which is a required property.
b) Even if its available / defaults to, its an overhead from AWS
simplicity.
--
Consultant Engineering
Team: HPCS-Vertica
Location: Noida, India
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] Jenkins randomly fails?
Hi Mike, This tutorial is very helpful to me. The chapter[1] you mentioned is also detailed, but I didn't read it carefully ... Thanks, Siming [1]: https://wiki.openstack.org/wiki/GerritJenkinsGit#Test_Failures On Thu, Nov 7, 2013 at 3:47 PM, Michael Bright mjbrigh...@gmail.com wrote: Hi Siming, Yes there are some intermittent test failures which may be due to infrastructure and/or bugs. Here's my suggestion from recent experiences as a Noob. The e-mail you got from Jenkins includes this line, with a link telling you what to do: Build failed. For information on how to proceed, see https://wiki.openstack.org/wiki/GerritJenkinsGit#Test_Failures In your case, at least for https://review.openstack.org/#/c/55370/ it seems that the build system recognized the failure as likely being due to a known bug #1239637. You should check the failing log file, which you can access via the link given in the e-mail or on the above 55370 change page: - check-tempest-devstack-vm-neutron-pghttp://logs.openstack.org/70/55370/1/check/check-tempest-devstack-vm-neutron-pg/6d4cc81 FAILURE in 18m 27s to verify that this is indeed the same bug which has caused your build to fail. If this is the case, you can click on the Review button (for your patch set) and set Code to 0, add a comment (Cover Message): Recheck bug #x that's Recheck bug #1239637 in your case (the bug number suggested by the Elastic recheck). Hopefully that will pass. I hope this helps, I'm learning too ... Regards, Mike. On 7 November 2013 08:09, Siming Yin sael...@gmail.com wrote: Hi all, Please have a look at these two changes: https://review.openstack.org/#/c/55370/ https://review.openstack.org/#/c/55221/ The only change is to remove 4 duplicate definitions. I'm sure this will not cause any new problems, but it seems like the tests are randomly failing in jenkins. Could anyone tell me how to handle this? Thanks, Siming ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [tempest] Get more info about undocumented API calls
Hi all, I'd like to fill some gaps in Tempest [1], but a lot of those calls are rarely documented. If you are a bit familiar with some of that, please write down note about that - tt will help me to write down test for it. My working copy of that sheet [2] is not fully synchronized with original [1], but it already contains some notes, insights. Thank you for helping, Martin [1] https://docs.google.com/spreadsheet/ccc?key=0AmYuZ6T4IJETdEVNTWlYVUVOWURmOERSZ0VGc1BBQWcusp=drive_web#gid=0 [2] https://docs.google.com/spreadsheet/ccc?key=0AnKZ7oAMtsxsdFFibDItWmhMV1BNUTlVMERXSDYxd0Eusp=drive_web#gid=0 Note: Everyone with link [1|2] can edit content. -- Martin Pavlásek mpavl...@redhat.com OpenStack Associate Quality Engineer Red Hat Czech / BRQ irc: mpavlase ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Heat] How do i implement this usecase:
Hi,
The OS::Neutron::FloatingIP resource works in the same manner as the
'neutron floating-create' command so currently there is no way to avoid
passing the floating network id. The AWS::EC2::EIP resource doesn't
require it because it uses the Nova API to allocate floating IPs. In
turn, Nova API knowns the floating network with the
default_floating_pool parameter defined in your nova.conf file.
I guess what you are looking for is a OS::Nova::FloatingIP resource. As
a workaround, you could leverage environments [1] and map to the EC2 EIP
resource:
resource_registry:
OS::Nova::FloatingIP: AWS::EC2::EIP
Simon
[1] http://docs.openstack.org/developer/heat/template_guide/environment.html
Le 07/11/2013 09:33, Nilakhya a écrit :
Currently my heat template works with AWS resource type:
DatabaseIPAddress:
Type: AWS::EC2::EIP
DatabaseIPAssoc :
Type: AWS::EC2::EIPAssociation
Properties:
InstanceId: {Ref: BaseInstance}
EIP: {Ref: MyIPAddress}
Now if i want to change to OpenStack ( OS ) namespace with a similar
implementation :
MyIPAddress:
Type: OS::Neutron::FloatingIP
Properties:
floating_network_id : String
MyIPAssoc :
Type: OS::Neutron::FloatingIPAssociation
Properties:
floatingip_id : {Ref: MyIPAddress}
I cannot problem is,
a) floating_network_id ( is not known ) which is a required property.
b) Even if its available / defaults to, its an overhead from AWS simplicity.
--
Consultant Engineering
Team: HPCS-Vertica
Location: Noida, India
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Simon Pasquier
Software Engineer
Bull, Architect of an Open World
Phone: + 33 4 76 29 71 49
http://www.bull.com
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] nova-api fails to start
Hi, I was trying to install the devstack and it failed while starting the nova api. below is a snippet from the console. Is it a bug? + screen -S stack -p n-api -X stuff 'cd /opt/stack/nova /usr/local/bin/nova-a'i || echo n-api failed to start | tee /opt/stack/status/stack/n-api.failure + echo 'Waiting for nova-api to start...' Waiting for nova-api to start... + wait_for_service 60 http://10.0.2.15:8774 + local timeout=60 + local url=http://10.0.2.15:8774 + timeout 60 sh -c 'while ! curl --noproxy '\''*'\'' -s http://10.0.2.15:8774 /dev/null; do sleep 1; done' + die 628 'nova-api did not start' + local exitcode=0 + set +o xtrace [Call Trace] ./stack.sh:1084:start_nova_api /home/krish/devstack/lib/nova:628:die [ERROR] /home/krish/devstack/lib/nova:628 nova-api did not start krish@krish-VirtualBox:~/devstack$ -- Krishanu ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [swift] what does swift do if the auditor find that all 3 replicas are corrupt?
On 11/7/13 5:59 AM, Daniel Li wrote: Thanks very much for your help, and please see my inline comments/questions. On Thu, Nov 7, 2013 at 2:30 AM, Samuel Merritt s...@swiftstack.com mailto:s...@swiftstack.com wrote: On 11/6/13 7:12 AM, Daniel Li wrote: Hi, I have a question about swift: what does swift do if the auditor find that all 3 replicas are corrupt? will it notify the owner of the object(email to the account owner)? what will happen if the GET request to the corrupted object? will it return a special error telling that all the replicas are corrupted? Or will it just say that the object is not exist? Or it just return one of the corrupted replica? Or something else? If all 3 (or N) replicas are corrupt, then the auditors will eventually quarantine all of them, and subsequent GET requests will receive 404 responses. No notifications are sent, nor is it really feasible to start sending them. The auditor is not a single process; there is one Swift auditor process running on each node in a cluster. Therefore, when an object is quarantined, there's no way for its auditor to know if the other copies are okay or not. Note that this is highly unlikely to ever happen, at least with the default of 3 replicas. When an auditor finds a corrupt object, it quarantines it (moves it to a quarantines directory). Did you mean that when the auditor found the corruption, it did not copy good replica from other object server to overwrite the corrupted one, it just moved it to a quarantines directory? That is correct. The object auditors don't perform any network IO, and in fact do not use the ring at all. All they do is scan the filesystems and quarantine bad objects in an infinite loop. (Of course, there are also container and account auditors that do similar things, but for container and account databases.) Then, since that object is missing, the replication processes will recreate the object by copying it from a node with a good copy. When did the replication processes recreated the object by copying it from a node with a good copy? Does the auditor send a message to replication so the replication will do the copy immediately? And what is a 'good' copy? Does the good copy's MD5 value is checked before copying? It'll happen whenever the other replicators, which are running on other nodes, get around to it. Replication in Swift is push-based, not pull-based; there is no receiver here to which a message could be sent. Currently, a good copy is one that hasn't been quarantined. Since replication uses rsync to push files around the network, there's no checking of MD5 at copy time. However, there is work underway to develop a replication protocol that avoids rsync entirely and uses the object server throughout the entire replication process, and that would give the object server a chance to check MD5 checksums on incoming writes. Note that this is only important should 2 replicas experience near-simultaneous bitrot; in that case, there is a chance that bad-copy A will get quarantined and replaced with bad-copy B. Eventually, though, a bad copy will get quarantined and replaced with a good copy, and then you've got 2 good copies and 1 bad one, which reduces to a previously-discussed scenario. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] nova-api fails to start
Any other recommendations on how to have a successful devstack
installation?
On Thu, Nov 7, 2013 at 11:37 PM, Krishanu Dhar rony.k...@gmail.com wrote:
below is an error that's probably the cause...
2013-11-07 23:24:14.758 TRACE nova IOError: [Errno 13] Permission denied:
'/etc/nova/api-paste.ini'
2013-11-07 23:24:14.758 TRACE nova
n-api failed to start
krish@krish-VirtualBox:/opt/stack/nova$ ls -l /etc/nova/api-paste.ini
-rw--- 1 nova nova 4260 Apr 23 2013 /etc/nova/api-paste.ini
isn't it expected to fail if the file is owned by nova... weird.
On Thu, Nov 7, 2013 at 11:18 PM, Krishanu Dhar rony.k...@gmail.comwrote:
it did not even start the process in my case.
I tried looking up email threads in google and looks like quite a few
have run into this before, but couldn't find a working fix.
On Thu, Nov 7, 2013 at 11:15 PM, Telles Nobrega
tellesnobr...@gmail.comwrote:
Weird, i had the same problem, but when i kill the processes it works
On Thu, Nov 7, 2013 at 2:34 PM, Krishanu Dhar rony.k...@gmail.comwrote:
Nothing was left behind.
#ps aux|grep -ie nova did not return anything.
On Thu, Nov 7, 2013 at 11:01 PM, Telles Nobrega
tellesnobr...@gmail.com wrote:
Did you check if there are any nova process left running?
On Thu, Nov 7, 2013 at 2:28 PM, Krishanu Dhar rony.k...@gmail.comwrote:
Appreciate the responses. But there is something wrong with this. I
ran unstack.sh again and retried the installation. it failed with the
same
message.
So, what are my options right now?
On Thu, Nov 7, 2013 at 7:31 PM, Telles Nobrega
tellesnobr...@gmail.com wrote:
Sometimes after ./unstack is ran, some process are still runnning
for nova.
Try running this to kill them all (ps aux | grep -ie nova | awk
'{print $2}' | xargs kill -9) and try ./stack again
On Thu, Nov 7, 2013 at 9:14 AM, Noorul Islam K M
noo...@noorul.comwrote:
Krishanu Dhar rony.k...@gmail.com writes:
Hi,
I was trying to install the devstack and it failed while starting
the nova
api. below is a snippet from the console. Is it a bug?
+ screen -S stack -p n-api -X stuff 'cd /opt/stack/nova
/usr/local/bin/nova-a'i || echo n-api failed to start | tee
/opt/stack/status/stack/n-api.failure
+ echo 'Waiting for nova-api to start...'
Waiting for nova-api to start...
+ wait_for_service 60 http://10.0.2.15:8774
+ local timeout=60
+ local url=http://10.0.2.15:8774
+ timeout 60 sh -c 'while ! curl --noproxy '\''*'\'' -s
http://10.0.2.15:8774 /dev/null; do sleep 1; done'
+ die 628 'nova-api did not start'
+ local exitcode=0
+ set +o xtrace
[Call Trace]
./stack.sh:1084:start_nova_api
/home/krish/devstack/lib/nova:628:die
[ERROR] /home/krish/devstack/lib/nova:628 nova-api did not start
krish@krish-VirtualBox:~/devstack$
Did you try screen -x stack ?
Regards,
Noorul
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
--
Telles Mota Vidal Nobrega
Developer at PulsarOpenStack Project - HP/LSD-UFCG
--
Krishanu
--
--
Telles Mota Vidal Nobrega
Developer at PulsarOpenStack Project - HP/LSD-UFCG
--
Krishanu
--
--
Telles Mota Vidal Nobrega
Developer at PulsarOpenStack Project - HP/LSD-UFCG
--
Krishanu
--
Krishanu
--
Krishanu
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] nova-api fails to start
Hi, I had the same issue and fixed that doing a chwon and changing the
ownership to my user of the files in /etc/nova where the owner was the user
nova.
In my case the files were: api-paste.ini and policy.json
I posted the solution there too:
http://stackoverflow.com/questions/19843239/getting-nova628die-trying-to-start-openstack-nova-module
Thanks
From: Krishanu Dhar [mailto:rony.k...@gmail.com]
Sent: Thursday, November 07, 2013 3:40 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] nova-api fails to start
Any other recommendations on how to have a successful devstack installation?
On Thu, Nov 7, 2013 at 11:37 PM, Krishanu Dhar
rony.k...@gmail.commailto:rony.k...@gmail.com wrote:
below is an error that's probably the cause...
2013-11-07 23:24:14.758 TRACE nova IOError: [Errno 13] Permission denied:
'/etc/nova/api-paste.ini'
2013-11-07 23:24:14.758 TRACE nova
n-api failed to start
krish@krish-VirtualBox:/opt/stack/nova$ ls -l /etc/nova/api-paste.ini
-rw--- 1 nova nova 4260 Apr 23 2013 /etc/nova/api-paste.ini
isn't it expected to fail if the file is owned by nova... weird.
On Thu, Nov 7, 2013 at 11:18 PM, Krishanu Dhar
rony.k...@gmail.commailto:rony.k...@gmail.com wrote:
it did not even start the process in my case.
I tried looking up email threads in google and looks like quite a few have run
into this before, but couldn't find a working fix.
On Thu, Nov 7, 2013 at 11:15 PM, Telles Nobrega
tellesnobr...@gmail.commailto:tellesnobr...@gmail.com wrote:
Weird, i had the same problem, but when i kill the processes it works
On Thu, Nov 7, 2013 at 2:34 PM, Krishanu Dhar
rony.k...@gmail.commailto:rony.k...@gmail.com wrote:
Nothing was left behind.
#ps aux|grep -ie nova did not return anything.
On Thu, Nov 7, 2013 at 11:01 PM, Telles Nobrega
tellesnobr...@gmail.commailto:tellesnobr...@gmail.com wrote:
Did you check if there are any nova process left running?
On Thu, Nov 7, 2013 at 2:28 PM, Krishanu Dhar
rony.k...@gmail.commailto:rony.k...@gmail.com wrote:
Appreciate the responses. But there is something wrong with this. I ran
unstack.sh again and retried the installation. it failed with the same message.
So, what are my options right now?
On Thu, Nov 7, 2013 at 7:31 PM, Telles Nobrega
tellesnobr...@gmail.commailto:tellesnobr...@gmail.com wrote:
Sometimes after ./unstack is ran, some process are still runnning for nova.
Try running this to kill them all (ps aux | grep -ie nova | awk '{print $2}' |
xargs kill -9) and try ./stack again
On Thu, Nov 7, 2013 at 9:14 AM, Noorul Islam K M
noo...@noorul.commailto:noo...@noorul.com wrote:
Krishanu Dhar rony.k...@gmail.commailto:rony.k...@gmail.com writes:
Hi,
I was trying to install the devstack and it failed while starting the nova
api. below is a snippet from the console. Is it a bug?
+ screen -S stack -p n-api -X stuff 'cd /opt/stack/nova
/usr/local/bin/nova-a'i || echo n-api failed to start | tee
/opt/stack/status/stack/n-api.failure
+ echo 'Waiting for nova-api to start...'
Waiting for nova-api to start...
+ wait_for_service 60 http://10.0.2.15:8774
+ local timeout=60
+ local url=http://10.0.2.15:8774
+ timeout 60 sh -c 'while ! curl --noproxy '\''*'\'' -s
http://10.0.2.15:8774 /dev/null; do sleep 1; done'
+ die 628 'nova-api did not start'
+ local exitcode=0
+ set +o xtrace
[Call Trace]
./stack.sh:1084:start_nova_api
/home/krish/devstack/lib/nova:628:die
[ERROR] /home/krish/devstack/lib/nova:628 nova-api did not start
krish@krish-VirtualBox:~/devstack$
Did you try screen -x stack ?
Regards,
Noorul
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.orgmailto:OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
--
Telles Mota Vidal Nobrega
Developer at PulsarOpenStack Project - HP/LSD-UFCG
--
Krishanu
--
--
Telles Mota Vidal Nobrega
Developer at PulsarOpenStack Project - HP/LSD-UFCG
--
Krishanu
--
--
Telles Mota Vidal Nobrega
Developer at PulsarOpenStack Project - HP/LSD-UFCG
--
Krishanu
--
Krishanu
--
Krishanu
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] nova-api fails to start
thanks man, incidentally i ran into your post too and it got me going.
However, I was wondering if the fix should go in stack.sh.stack.sh
On Fri, Nov 8, 2013 at 12:32 AM, Cazzolato, Sergio J
sergio.j.cazzol...@intel.com wrote:
Hi, I had the same issue and fixed that doing a chwon and changing the
ownership to my user of the files in /etc/nova where the owner was the user
nova.
In my case the files were: api-paste.ini and policy.json
I posted the solution there too:
http://stackoverflow.com/questions/19843239/getting-nova628die-trying-to-start-openstack-nova-module
Thanks
*From:* Krishanu Dhar [mailto:rony.k...@gmail.com]
*Sent:* Thursday, November 07, 2013 3:40 PM
*To:* OpenStack Development Mailing List (not for usage questions)
*Subject:* Re: [openstack-dev] nova-api fails to start
Any other recommendations on how to have a successful devstack
installation?
On Thu, Nov 7, 2013 at 11:37 PM, Krishanu Dhar rony.k...@gmail.com
wrote:
below is an error that's probably the cause...
2013-11-07 23:24:14.758 TRACE nova IOError: [Errno 13] Permission denied:
'/etc/nova/api-paste.ini'
2013-11-07 23:24:14.758 TRACE nova
n-api failed to start
krish@krish-VirtualBox:/opt/stack/nova$ ls -l /etc/nova/api-paste.ini
-rw--- 1 nova nova 4260 Apr 23 2013 /etc/nova/api-paste.ini
isn't it expected to fail if the file is owned by nova... weird.
On Thu, Nov 7, 2013 at 11:18 PM, Krishanu Dhar rony.k...@gmail.com
wrote:
it did not even start the process in my case.
I tried looking up email threads in google and looks like quite a few have
run into this before, but couldn't find a working fix.
On Thu, Nov 7, 2013 at 11:15 PM, Telles Nobrega tellesnobr...@gmail.com
wrote:
Weird, i had the same problem, but when i kill the processes it works
On Thu, Nov 7, 2013 at 2:34 PM, Krishanu Dhar rony.k...@gmail.com wrote:
Nothing was left behind.
#ps aux|grep -ie nova did not return anything.
On Thu, Nov 7, 2013 at 11:01 PM, Telles Nobrega tellesnobr...@gmail.com
wrote:
Did you check if there are any nova process left running?
On Thu, Nov 7, 2013 at 2:28 PM, Krishanu Dhar rony.k...@gmail.com wrote:
Appreciate the responses. But there is something wrong with this. I ran
unstack.sh again and retried the installation. it failed with the same
message.
So, what are my options right now?
On Thu, Nov 7, 2013 at 7:31 PM, Telles Nobrega tellesnobr...@gmail.com
wrote:
Sometimes after ./unstack is ran, some process are still runnning for
nova.
Try running this to kill them all (ps aux | grep -ie nova | awk '{print
$2}' | xargs kill -9) and try ./stack again
On Thu, Nov 7, 2013 at 9:14 AM, Noorul Islam K M noo...@noorul.com
wrote:
Krishanu Dhar rony.k...@gmail.com writes:
Hi,
I was trying to install the devstack and it failed while starting the
nova
api. below is a snippet from the console. Is it a bug?
+ screen -S stack -p n-api -X stuff 'cd /opt/stack/nova
/usr/local/bin/nova-a'i || echo n-api failed to start | tee
/opt/stack/status/stack/n-api.failure
+ echo 'Waiting for nova-api to start...'
Waiting for nova-api to start...
+ wait_for_service 60 http://10.0.2.15:8774
+ local timeout=60
+ local url=http://10.0.2.15:8774
+ timeout 60 sh -c 'while ! curl --noproxy '\''*'\'' -s
http://10.0.2.15:8774 /dev/null; do sleep 1; done'
+ die 628 'nova-api did not start'
+ local exitcode=0
+ set +o xtrace
[Call Trace]
./stack.sh:1084:start_nova_api
/home/krish/devstack/lib/nova:628:die
[ERROR] /home/krish/devstack/lib/nova:628 nova-api did not start
krish@krish-VirtualBox:~/devstack$
Did you try screen -x stack ?
Regards,
Noorul
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
--
Telles Mota Vidal Nobrega
Developer at PulsarOpenStack Project - HP/LSD-UFCG
--
Krishanu
--
--
Telles Mota Vidal Nobrega
Developer at PulsarOpenStack Project - HP/LSD-UFCG
--
Krishanu
--
--
Telles Mota Vidal Nobrega
Developer at PulsarOpenStack Project - HP/LSD-UFCG
--
Krishanu
--
Krishanu
--
Krishanu
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Krishanu
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] L3 advanced features blueprint mapping to IETF and IEEE standards
From: Pedro Roque Marques [mailto:pedro.r.marq...@gmail.com] Colin, The nice thing about standards is that there are so many of them to choose from. For instance, if you take this Internet Draft: http://tools.ietf.org/html/draft-ietf-l3vpn-end-system-02 which is based on RFC4364. It has already been implemented as a Neutron plugin via OpenContrail (http://juniper.github.io/contrail-vnc/README.html); With this implementation each OpenStack cluster can be configured as its own Autonomous System. There is a blueprint https://blueprints.launchpad.net/neutron/+spec/neutron-bgp-mpls-vpn that is discussing adding the provisioning of the autonomous system and peering to Neutron. Please note that the work above does interoperate with 4364 using option B. Option C is possible but not that practical (as an operator you probably don't want to expose your internal topology between clusters). If you want to give it a try you can use this devstack fork: https://github.com/dsetia/devstack. You can use it to interoperate with a standard router that implements 4364 and support MPLS over GRE. Products from cisco/juniper/ALU/huwawei etc do. I believe that the work i'm referencing implements interoperability while having very minimal changes to Neutron. It is based on the same concept of neutron virtual network and it hides the BGP/MPLS functionality from the user by translating policies that establish connectivity between virtual networks into RFC 4364 concepts. Please refer to: https://blueprints.launchpad.net/neutron/+spec/policy-extensions-for-neutron Would it make sense to have an IRC/Web meeting around interoperability with RFC4364 an OpenStack managed clusters ? I believe that there is a lot of work that has already been done there by multiple vendors as well as some carriers. +1 And it should be scheduled and announced a reasonable time in advance developers can plan to participate. --Rocky Pedro. On Nov 7, 2013, at 12:35 AM, Colin McNamara co...@2cups.commailto:co...@2cups.com wrote: I have a couple concerns that I don't feel I clearly communicated during the L3 advanced features session. I'd like to take this opportunity to both clearly communicate my thoughts, as well as start a discussion around them. Building to the edge of the autonomous system The current state of neutron implementation is functionally the l2 domain and simple l3 services that are part of a larger autonomous system. The routers and switches northbound of the OpenStack networking layer handled the abstraction and integration of the components. Note, I use the term Autonomous System to describe more then the notion of BGP AS, but more broadly in the term of a system that is controlled within a common framework and methodology, and integrates with a peer system that doesn't not share that same scope or method of control These components that composed the autonomous system boundary implement protocols and standards that map into IETF and IEEE standards. The reasoning for this is interoperability. Before vendors utilize IETF for interoperability at this layer, the provider experience was horrible (this was my personal experience in the late 90's). Wednesdays discussions in the Neutron Design Sessions A couple of the discussions, most notably the extension of l3 functionality fell within the scope of starting the process of extending Neutron with functionality that will result (eventually) in the ability for an OpenStack installation to operate as it's own Autonomous System. The discussions that occurred to support L3 advanced functionality (northbound boundary), and the QOS extension functionality both fell into the scope of Northbound and Southbound boundaries of this system. My comments in the session My comments in the session, while clouded with jet-lag were specifically around two concepts that are used when integrating other types of systems 1. In a simple (1-8) tenant environment integration with a northbound AS is normally done in a PE-CE model that generally centers around mapping dot1q tags into the appropriate northbound l3 segments and then handling the availability of the L2 path that traverses with port channeling, MLAG, STP, Etc. 2. In a complex environment (8+ for discussion) different Carrier Supporting Carrier (CSC) methods defined in IETF RFC 4364 Section 10 type A, B or C are used. These allow the mapping of segregated tenant networks together and synchronizing between distributed systems. This normally extends the tagging or tunneling mechanism and then allows for BGP to synchronize NLRI information between AS's. These are the standard ways of integrating between carriers, but also components of these implementations are used to integrate and scale inside of a single web scale data center. Commonly when you scale beyond a certain physical port boundary (1000is edge ports in many implementations, much larger in current implementations) the same designs
Re: [openstack-dev] Bad review patterns
On 7 November 2013 13:15, Day, Phil philip@hp.com wrote: Core reviewers look for the /comments/ from people, not just the votes. A +1 from someone that isn't core is meaningless unless they are known to be a thoughtful code reviewer. A -1 with no comment is also bad, because it doesn't help the reviewee get whatever the issue is fixed. It's very much not OK to spend an hour reviewing something and then +1 with no comment: if I, and I think any +2er across the project see a patch that needs an hour of review, with a commentless +1, we'll likely discount the +1 as being meaningful. I don't really get what you're saying here Rob. It seems to me an almost inevitable part of the review process that useful comments are going to be mostly negative. If someone has invested that amount of effort because the patch is complex, or It took then a while to work their way back into that part of the systems, etc, but having given the code careful consideration they decide it's good - do you want comments in there saying I really like your code, Well done on fixing such a complex problem or some such ? Negative comments are fine: I was saying that statistically, having an hour-long patch (which BTW puts it waaay past the diminishing returns on patch size tradeoff) to review and then having nothing at all to say about it is super suspect. Sure, having nothing to say on a 10 line patch - hit a +1, move on. But something that takes an hour to review? I'd expect at minimum the thing to prompt some suggestions *even while it gets a +1*. I just don't see how you can use a lack or presence of positive feedback in a +1 as any sort of indication on the quality of that +1. Unless you start asking reviewers to précis the change in their own words to show that they understood it I don't really see how additional positive comments help in most cases. Perhaps if you have some specific examples of this it would help to clarify It might even be negative feedback. Like - this patch is correct but the fact it had to be done as one patch shows our code structure here is wonky. If you could follow up with something to let us avoid future mammoth patches, that would be awesome. Again, I'm talking about hour long reviews, which is the example Radomir gave. Another way of presenting what I'm saying is this: Code reviews are a dialogue. How often in a discussion with a live human would you have no feedback at all, if they were reading a speech to you. You might go 'that was a great speech' (+2) and *still* have something to add. As an observer given a very long speech, and an audience, I'd suspect folk went to sleep if they didn't have commentary :) -Rob -- Robert Collins rbtcoll...@hp.com Distinguished Technologist HP Converged Cloud ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Bad review patterns
On 8 November 2013 00:02, Radomir Dopieralski openst...@sheep.art.pl wrote: I created a page on the wiki, https://wiki.openstack.org/wiki/CodeReviewGuidelines I put some initial content there, based on the discussion in this thread. Please feel free to discuss those points further here, and to amend that page and add to it. Thank you. I thought we might have a similar page already, but I only found: https://wiki.openstack.org/wiki/ReviewChecklist [what to look for] and https://wiki.openstack.org/wiki/ReviewWorkflowTips [what reviewees should do] I suspect we probably need to tie all three together somehow. Any ideas of where we could put a link to it? I'm thinking about the Gerrit Workflow page, maybe also some pages specific to particular teams (I've seen there is a page with review tips for Nova). So https://wiki.openstack.org/wiki/Gerrit_Workflow and the ReviewWorkflowTips page above overlap a lot. I think we should merge ReviewWorkflowTips into Gerrit_Workflow, and link to the review checklist and guidlines pages from Gerrit_Workflow. -Rob -- Robert Collins rbtcoll...@hp.com Distinguished Technologist HP Converged Cloud ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] nova-api fails to start
Now i have something like your problem, im getting
die 609 'nova-api did not start'
On Thu, Nov 7, 2013 at 4:11 PM, Krishanu Dhar rony.k...@gmail.com wrote:
thanks man, incidentally i ran into your post too and it got me going.
However, I was wondering if the fix should go in stack.sh.stack.sh
On Fri, Nov 8, 2013 at 12:32 AM, Cazzolato, Sergio J
sergio.j.cazzol...@intel.com wrote:
Hi, I had the same issue and fixed that doing a chwon and changing the
ownership to my user of the files in /etc/nova where the owner was the user
nova.
In my case the files were: api-paste.ini and policy.json
I posted the solution there too:
http://stackoverflow.com/questions/19843239/getting-nova628die-trying-to-start-openstack-nova-module
Thanks
*From:* Krishanu Dhar [mailto:rony.k...@gmail.com]
*Sent:* Thursday, November 07, 2013 3:40 PM
*To:* OpenStack Development Mailing List (not for usage questions)
*Subject:* Re: [openstack-dev] nova-api fails to start
Any other recommendations on how to have a successful devstack
installation?
On Thu, Nov 7, 2013 at 11:37 PM, Krishanu Dhar rony.k...@gmail.com
wrote:
below is an error that's probably the cause...
2013-11-07 23:24:14.758 TRACE nova IOError: [Errno 13] Permission denied:
'/etc/nova/api-paste.ini'
2013-11-07 23:24:14.758 TRACE nova
n-api failed to start
krish@krish-VirtualBox:/opt/stack/nova$ ls -l /etc/nova/api-paste.ini
-rw--- 1 nova nova 4260 Apr 23 2013 /etc/nova/api-paste.ini
isn't it expected to fail if the file is owned by nova... weird.
On Thu, Nov 7, 2013 at 11:18 PM, Krishanu Dhar rony.k...@gmail.com
wrote:
it did not even start the process in my case.
I tried looking up email threads in google and looks like quite a few
have run into this before, but couldn't find a working fix.
On Thu, Nov 7, 2013 at 11:15 PM, Telles Nobrega tellesnobr...@gmail.com
wrote:
Weird, i had the same problem, but when i kill the processes it works
On Thu, Nov 7, 2013 at 2:34 PM, Krishanu Dhar rony.k...@gmail.com
wrote:
Nothing was left behind.
#ps aux|grep -ie nova did not return anything.
On Thu, Nov 7, 2013 at 11:01 PM, Telles Nobrega tellesnobr...@gmail.com
wrote:
Did you check if there are any nova process left running?
On Thu, Nov 7, 2013 at 2:28 PM, Krishanu Dhar rony.k...@gmail.com
wrote:
Appreciate the responses. But there is something wrong with this. I ran
unstack.sh again and retried the installation. it failed with the same
message.
So, what are my options right now?
On Thu, Nov 7, 2013 at 7:31 PM, Telles Nobrega tellesnobr...@gmail.com
wrote:
Sometimes after ./unstack is ran, some process are still runnning for
nova.
Try running this to kill them all (ps aux | grep -ie nova | awk '{print
$2}' | xargs kill -9) and try ./stack again
On Thu, Nov 7, 2013 at 9:14 AM, Noorul Islam K M noo...@noorul.com
wrote:
Krishanu Dhar rony.k...@gmail.com writes:
Hi,
I was trying to install the devstack and it failed while starting the
nova
api. below is a snippet from the console. Is it a bug?
+ screen -S stack -p n-api -X stuff 'cd /opt/stack/nova
/usr/local/bin/nova-a'i || echo n-api failed to start | tee
/opt/stack/status/stack/n-api.failure
+ echo 'Waiting for nova-api to start...'
Waiting for nova-api to start...
+ wait_for_service 60 http://10.0.2.15:8774
+ local timeout=60
+ local url=http://10.0.2.15:8774
+ timeout 60 sh -c 'while ! curl --noproxy '\''*'\'' -s
http://10.0.2.15:8774 /dev/null; do sleep 1; done'
+ die 628 'nova-api did not start'
+ local exitcode=0
+ set +o xtrace
[Call Trace]
./stack.sh:1084:start_nova_api
/home/krish/devstack/lib/nova:628:die
[ERROR] /home/krish/devstack/lib/nova:628 nova-api did not start
krish@krish-VirtualBox:~/devstack$
Did you try screen -x stack ?
Regards,
Noorul
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
--
Telles Mota Vidal Nobrega
Developer at PulsarOpenStack Project - HP/LSD-UFCG
--
Krishanu
--
--
Telles Mota Vidal Nobrega
Developer at PulsarOpenStack Project - HP/LSD-UFCG
--
Krishanu
--
--
Telles Mota Vidal Nobrega
Developer at PulsarOpenStack Project - HP/LSD-UFCG
--
Krishanu
--
Krishanu
--
Krishanu
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Krishanu
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
--
Telles
Re: [openstack-dev] nova-api fails to start
Hey Telies - Were you trying to recreate the failure? or is it a new
installation?
On Fri, Nov 8, 2013 at 2:13 AM, Telles Nobrega tellesnobr...@gmail.comwrote:
Now i have something like your problem, im getting
die 609 'nova-api did not start'
On Thu, Nov 7, 2013 at 4:11 PM, Krishanu Dhar rony.k...@gmail.com wrote:
thanks man, incidentally i ran into your post too and it got me going.
However, I was wondering if the fix should go in stack.sh.stack.sh
On Fri, Nov 8, 2013 at 12:32 AM, Cazzolato, Sergio J
sergio.j.cazzol...@intel.com wrote:
Hi, I had the same issue and fixed that doing a chwon and changing the
ownership to my user of the files in /etc/nova where the owner was the user
nova.
In my case the files were: api-paste.ini and policy.json
I posted the solution there too:
http://stackoverflow.com/questions/19843239/getting-nova628die-trying-to-start-openstack-nova-module
Thanks
*From:* Krishanu Dhar [mailto:rony.k...@gmail.com]
*Sent:* Thursday, November 07, 2013 3:40 PM
*To:* OpenStack Development Mailing List (not for usage questions)
*Subject:* Re: [openstack-dev] nova-api fails to start
Any other recommendations on how to have a successful devstack
installation?
On Thu, Nov 7, 2013 at 11:37 PM, Krishanu Dhar rony.k...@gmail.com
wrote:
below is an error that's probably the cause...
2013-11-07 23:24:14.758 TRACE nova IOError: [Errno 13] Permission
denied: '/etc/nova/api-paste.ini'
2013-11-07 23:24:14.758 TRACE nova
n-api failed to start
krish@krish-VirtualBox:/opt/stack/nova$ ls -l /etc/nova/api-paste.ini
-rw--- 1 nova nova 4260 Apr 23 2013 /etc/nova/api-paste.ini
isn't it expected to fail if the file is owned by nova... weird.
On Thu, Nov 7, 2013 at 11:18 PM, Krishanu Dhar rony.k...@gmail.com
wrote:
it did not even start the process in my case.
I tried looking up email threads in google and looks like quite a few
have run into this before, but couldn't find a working fix.
On Thu, Nov 7, 2013 at 11:15 PM, Telles Nobrega tellesnobr...@gmail.com
wrote:
Weird, i had the same problem, but when i kill the processes it works
On Thu, Nov 7, 2013 at 2:34 PM, Krishanu Dhar rony.k...@gmail.com
wrote:
Nothing was left behind.
#ps aux|grep -ie nova did not return anything.
On Thu, Nov 7, 2013 at 11:01 PM, Telles Nobrega tellesnobr...@gmail.com
wrote:
Did you check if there are any nova process left running?
On Thu, Nov 7, 2013 at 2:28 PM, Krishanu Dhar rony.k...@gmail.com
wrote:
Appreciate the responses. But there is something wrong with this. I ran
unstack.sh again and retried the installation. it failed with the same
message.
So, what are my options right now?
On Thu, Nov 7, 2013 at 7:31 PM, Telles Nobrega tellesnobr...@gmail.com
wrote:
Sometimes after ./unstack is ran, some process are still runnning for
nova.
Try running this to kill them all (ps aux | grep -ie nova | awk '{print
$2}' | xargs kill -9) and try ./stack again
On Thu, Nov 7, 2013 at 9:14 AM, Noorul Islam K M noo...@noorul.com
wrote:
Krishanu Dhar rony.k...@gmail.com writes:
Hi,
I was trying to install the devstack and it failed while starting the
nova
api. below is a snippet from the console. Is it a bug?
+ screen -S stack -p n-api -X stuff 'cd /opt/stack/nova
/usr/local/bin/nova-a'i || echo n-api failed to start | tee
/opt/stack/status/stack/n-api.failure
+ echo 'Waiting for nova-api to start...'
Waiting for nova-api to start...
+ wait_for_service 60 http://10.0.2.15:8774
+ local timeout=60
+ local url=http://10.0.2.15:8774
+ timeout 60 sh -c 'while ! curl --noproxy '\''*'\'' -s
http://10.0.2.15:8774 /dev/null; do sleep 1; done'
+ die 628 'nova-api did not start'
+ local exitcode=0
+ set +o xtrace
[Call Trace]
./stack.sh:1084:start_nova_api
/home/krish/devstack/lib/nova:628:die
[ERROR] /home/krish/devstack/lib/nova:628 nova-api did not start
krish@krish-VirtualBox:~/devstack$
Did you try screen -x stack ?
Regards,
Noorul
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
--
Telles Mota Vidal Nobrega
Developer at PulsarOpenStack Project - HP/LSD-UFCG
--
Krishanu
--
--
Telles Mota Vidal Nobrega
Developer at PulsarOpenStack Project - HP/LSD-UFCG
--
Krishanu
--
--
Telles Mota Vidal Nobrega
Developer at PulsarOpenStack Project - HP/LSD-UFCG
--
Krishanu
--
Krishanu
--
Krishanu
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Krishanu
___
OpenStack-dev mailing
Re: [openstack-dev] [Solum] Choice of API infrastructure
On 11/07/2013 07:28 AM, Jay Pipes wrote: Hey Doug, following up, but realize you are likely very busy at the summit :) On 11/04/2013 10:20 PM, Doug Hellmann wrote: On Tue, Nov 5, 2013 at 10:37 AM, Jay Pipes jaypi...@gmail.com The models defined in WSME are completely different from the database models, and should not be used outside of the API code. Think of them as declaring the models for the consumer of the API, rather than the implementer of the API. I don't really see the point of the distinction. At the end of the day, the consumer of the API is using the API to manipulate and retrieve data. That data is really the model, with some syntactic sugar like Atom links, etc. Even in a control API -- as opposed to a data API like Glance, Ceilometer or Swift -- the benefits of a heavy API layer like Pecan and WSME are pretty small, IMO. That approach binds your API tightly to the database representation, which we were trying to avoid. I wasn't referring to the database representation, actually. I was referring to the data model, which is different in that it abstracts away any underlying schema or storage engine... I would much rather see the Ceilometer models [1] actually be models that can validate the data that is used to construct the model object instead of having duplicated WSME models repeated in the WSGI controller code [2]. The reason is because if/when I decide to make a Ceilometer API that uses a different protocol, say AMQP, instead of HTTP, now I need to duplicate all of the validation code that WSME is providing on the data model layer... however if the validation was in the models themselves, I could easily create an API on a different protocol using just the models for validation. We do that in some cases. However, there is also a difference in some cases between the validation at the API layer (a value must be a number, or a UUID, etc.) and the validation in the database layer (a number must fall within a range or a UUID must refer to an existing object). So there is a place for both, and the validation done in the WSME classes is not meant to be the only validation performed. OK, understood. The benefits of declaring WSME classes include automatic serialization in JSON and XML, generating WADL files to be included in the API docs (work is already happening to make this available for everyone), and consistent input and output types for API endpoints (making it easier for consumers of the API to use it and for implementers to validate inputs and assume consistent defaults). I can't stand XML. I believe it should be retired to the dustbin of coding history, like Basic. You've made that clear in the past. :-) I agree, for what it's worth. Some of our users do seem to want it, and with WSME *you don't have to care*. Also understood. :) That said, consumers of a RESTful API don't care how the API is implemented. They care that it's documented and consistent, and if WSME makes API documentation easier, then that's A Good Thing, agreed. It's true that WSME includes some stuff to make validating inputs easier, but it does so, IMHO, at the expense of readability because everything is decorated and hidden away somewhere other than the models themselves. See note above... I'm not sure what that means. Hidden where? The validation is either described in the attribute specifier for the model, or in the model's class, or in the controller (depending on the scope of the rule being applied). Sorry, hidden wasn't the best word to describe that. I meant more it's less obvious to folks who expect to find validation of the data model at the data model layer :) And, to be clear, Pecan and WSME are integrated by Pecan can definitely be used without WSME. I included WSME in the proposal to replace the home-grown WSGI framework because I thought it added significant benefits, but it is not going to be appropriate for all situations (streaming large image files is one example). Yes, in one way it's a bit unfortanate that we're now comparing Falcon with Pecan + WSME as opposed to just comparing Falcon with Pecan and then evaluating whether WSME should be used (on top of either one...). It's unfortunate because we've spent all this email thread actually talking about WSME and not much at all about Pecan ;) Here's a third reason I don't care for Pecan/WSME: it uses Webob. Other than eventlet, I don't know of a single library that OpenStack projects have used over the years that we've had more issues with than Webob. Yes, I felt the pain of updating us to the latest WebOb. The project has evolved since those days, and the current maintainers are committed to not breaking the API. That
Re: [openstack-dev] [Solum]: Workshop dates at SFO
Based on what I am seeing on the doodle poll, we are sticking to the original dates for the workshop [Nov 19, 20] Eventbrite registration page https://www.eventbrite.com/event/9130831563 Etherpad planning page for the event https://etherpad.openstack.org/p/SolumSFOCommunityWorkshop See you all for a great set of discussions! From: Roshan Agrawal Sent: Wednesday, November 06, 2013 8:45 PM To: openstack-dev@lists.openstack.org Subject: [Solum]: Workshop dates at SFO Folks, some of us indicated they cannot make Nov 19,20, so I created a doodle poll to finalize a date that works for most of us. Please take a moment to indicate your preference on the doodle link below - http://www.doodle.com/6yey9nfgfapzv4f8 Please get this done by EOD if you can. Thanks, Roshan ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Swift] log line length
Is there any way for me to change the logging so that it doesn't truncate the output - so basically the length of the line printed to the log is not limited to a certain length? Thanks. Alex ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Solum] Choice of API infrastructure
Solum Team, First of all I wanted to say that I have been thinking a lot about this thread, and have been seeking input from a number of you who attended the Summit this week. I do *not* see this decision as a critical one, because if something really mattered a ton we could rip our one framework and put another in. What I love about this discussion is that we are having a healthy debate about different points of view, which was very thought provoking. I have heard input from skeptics who think that engineering decisions have to be made in a small group in order to be efficient. I know that thinking is wrong, and it's examples like these that convince me further that discussions like these help us make better choices, and make development more efficient over the long run. We should give the most weight to the preferences of the engineers who will write and maintain the code. If there are team members who are volunteering to write and maintain the bulk of our API code over a period of time who really want Falcon over Pecan, then we should give that fair consideration. The API is exceedingly important to Solum, and all of us will be working on it, so we need a choice that all of us can live with. I suggest that we settle on Pecan+WSME, for the following reasons: 1) It is a known quantity, and is likely to work well for Solum's needs, considering that Solum is primarily a control plane API system, and that performance is not a primary motivator. 2) Pecan+WSME allows us to offer data serializations in both JSON and XML to help satisfy the preferences of the API consumers. 3) It allows us to have multiple models that are loosely coupled, which can aid in data validation. 4) At this point in time, other OpenStack core/integrated/ecosystem projects are using Pecan+WSME, and several Solum contributors will be switching between projects. There is an advantage to a higher level of consistency among various projects. I accept that Webob may be problematic for us, that performance may be less than ideal, and that some Solum developers may dislike working with WSME, and that Falcon may actually be more pleasant to work with. We have team members with a deep understanding of Falcon, and could definitely make it work. We can proceed with Pecan+WSME accepting these (and other) trade-offs. Are there any other critically important considerations that we should consider before converging on this choice? I'd like to hear that input prior to our next IRC meeting. Thanks, Adrian On Nov 8, 2013, at 5:59 AM, Steven Dake sd...@redhat.com wrote: On 11/07/2013 07:28 AM, Jay Pipes wrote: Hey Doug, following up, but realize you are likely very busy at the summit :) On 11/04/2013 10:20 PM, Doug Hellmann wrote: On Tue, Nov 5, 2013 at 10:37 AM, Jay Pipes jaypi...@gmail.com The models defined in WSME are completely different from the database models, and should not be used outside of the API code. Think of them as declaring the models for the consumer of the API, rather than the implementer of the API. I don't really see the point of the distinction. At the end of the day, the consumer of the API is using the API to manipulate and retrieve data. That data is really the model, with some syntactic sugar like Atom links, etc. Even in a control API -- as opposed to a data API like Glance, Ceilometer or Swift -- the benefits of a heavy API layer like Pecan and WSME are pretty small, IMO. That approach binds your API tightly to the database representation, which we were trying to avoid. I wasn't referring to the database representation, actually. I was referring to the data model, which is different in that it abstracts away any underlying schema or storage engine... I would much rather see the Ceilometer models [1] actually be models that can validate the data that is used to construct the model object instead of having duplicated WSME models repeated in the WSGI controller code [2]. The reason is because if/when I decide to make a Ceilometer API that uses a different protocol, say AMQP, instead of HTTP, now I need to duplicate all of the validation code that WSME is providing on the data model layer... however if the validation was in the models themselves, I could easily create an API on a different protocol using just the models for validation. We do that in some cases. However, there is also a difference in some cases between the validation at the API layer (a value must be a number, or a UUID, etc.) and the validation in the database layer (a number must fall within a range or a UUID must refer to an existing object). So there is a place for both, and the validation done in the WSME classes is not meant to be the only validation performed. OK, understood. The benefits of declaring WSME classes include automatic serialization
Re: [openstack-dev] [Solum] Choice of API infrastructure
On 11/07/2013 06:41 PM, Adrian Otto wrote: Solum Team, First of all I wanted to say that I have been thinking a lot about this thread, and have been seeking input from a number of you who attended the Summit this week. I do *not* see this decision as a critical one, because if something really mattered a ton we could rip our one framework and put another in. What I love about this discussion is that we are having a healthy debate about different points of view, which was very thought provoking. I have heard input from skeptics who think that engineering decisions have to be made in a small group in order to be efficient. I know that thinking is wrong, and it's examples like these that convince me further that discussions like these help us make better choices, and make development more efficient over the long run. We should give the most weight to the preferences of the engineers who will write and maintain the code. If there are team members who are volunteering to write and maintain the bulk of our API code over a period of time who really want Falcon over Pecan, then we should give that fair consideration. The API is exceedingly important to Solum, and all of us will be working on it, so we need a choice that all of us can live with. I suggest that we settle on Pecan+WSME, for the following reasons: 1) It is a known quantity, and is likely to work well for Solum's needs, considering that Solum is primarily a control plane API system, and that performance is not a primary motivator. 2) Pecan+WSME allows us to offer data serializations in both JSON and XML to help satisfy the preferences of the API consumers. 3) It allows us to have multiple models that are loosely coupled, which can aid in data validation. 4) At this point in time, other OpenStack core/integrated/ecosystem projects are using Pecan+WSME, and several Solum contributors will be switching between projects. There is an advantage to a higher level of consistency among various projects. I accept that Webob may be problematic for us, that performance may be less than ideal, and that some Solum developers may dislike working with WSME, and that Falcon may actually be more pleasant to work with. We have team members with a deep understanding of Falcon, and could definitely make it work. We can proceed with Pecan+WSME accepting these (and other) trade-offs. Are there any other critically important considerations that we should consider before converging on this choice? I'd like to hear that input prior to our next IRC meeting. None that I can think of. I'll get behind the decision, then, and if all are in consensus, I'll abandon the Falcon API patch. We do need to get the Pecan/WSME patch to pass the gates though :) Doug, I'm hoping you might give Noorul a hand with that next week upon your return from Hong Kong? All the best, -jay ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Bad review patterns
On 11/07/2013 01:56 PM, James Bottomley wrote: On Thu, 2013-11-07 at 00:21 +, Day, Phil wrote: Leaving a mark. === You review a change and see that it is mostly fine, but you feel that since you did so much work reviewing it, you should at least find *something* wrong. So you find some nitpick and -1 the change just so that they know you reviewed it. This is quite obvious. Just don't do it. It's OK to spend an hour reviewing something, and then leaving no comments on it, because it's simply fine, or because we had to means to test someting (see the first pattern). Another one that comes into this category is adding a -1 which just says I agree with the other -1's in here. If you have some additional perspective and can expand on it then that's fine - otherwise it adds very little and is just review count chasing. It's an unfortunate consequence of counting and publishing review stats that having such a measure will inevitable also drive behavour. Perhaps a source of the problem is early voting. Feeling pressure to add a +/-1 (or even 2) without fully asking what's going on in the code leads to premature adjudication. For instance, I have to do a lot of reviews in SCSI; I'm a subject matter expert, so I do recognise some bad coding patterns and ask for them to be changed unconditionally, but a lot of the time I don't necessarily understand why the code was done in the way it was, so I ask. Before I get the answer I'm not really qualified to judge the merits. +1 to this. Realistically if I have questions in the code and am unsure how I'd score it I'll often leave a 0 review with questions inline to help me understand. I consider this generally good form, and it's helpful to everyone in the learning process about the code. -Sean -- Sean Dague http://dague.net signature.asc Description: OpenPGP digital signature ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Bad review patterns
On 11/07/2013 05:35 PM, Jiri Tomasek wrote: On 11/07/2013 08:25 AM, Daniel P. Berrange wrote: On Thu, Nov 07, 2013 at 12:21:38AM +, Day, Phil wrote: Leaving a mark. === You review a change and see that it is mostly fine, but you feel that since you did so much work reviewing it, you should at least find *something* wrong. So you find some nitpick and -1 the change just so that they know you reviewed it. This is quite obvious. Just don't do it. It's OK to spend an hour reviewing something, and then leaving no comments on it, because it's simply fine, or because we had to means to test someting (see the first pattern). Another one that comes into this category is adding a -1 which just says I agree with the other -1's in here. If you have some additional perspective and can expand on it then that's fine - otherwise it adds very little and is just review count chasing. I don't think that it is valueless as you describe. If I multiple people add '-1' with a same comments as name, then as a core reviewer I will consider that initial -1 to be a much stronger nack, than if only one person had added the -1. So I welcome people adding I agree with blah to any review. It's an unfortunate consequence of counting and publishing review stats that having such a measure will inevitable also drive behavour. IMHO what this shows is not people trying to game the stats, but rather the inadequacy of gerrit. We don't have any way to distinguish a -1 minor nice to have nitpick from a -1 serious code issue that is a must-fix. Adding a -2 is really too heavyweight because it is sticky, and implies do not ever merge this. It would be nice to be able to use '-2' for serious must-fix issue without it being sticky, and have a separate way for core reviewers to put an review into a block from being merged indefinitely state - perhaps a new state would be more useful eg a Blocked state, to add to New, Open, Merged, Abadoned. Daniel The comment describing the -1 should be enough to distinquish between minor nitpick and serious code issue IMHO. If it is a serious issue, other reviewers also giving -1 confirming the issue is probably a good thing. (Not with the minor nit though...) Agreed, the comments are there for a reason. It's also handy to provide forward looking statements to other reviewers in case you don't get back to the review queue right away. For instance when I know that might happen I tend to leave comments like I'm +2 after the following is addressed. That's also extremely helpful to provide incentive to the submitter to make those kinds of changes. Not all submissions fit into this kind of category, some really need to iterate through sets of issues to get ready for the code base. But when they are close, defining the end state for the contributor and other reviewers that won't feel like they need to wait for your comments on the updated review (because you clearly explained what you thought needed to change) is helpful. -Sean -- Sean Dague http://dague.net signature.asc Description: OpenPGP digital signature ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Bad review patterns
On 11/08/2013 01:37 AM, Pedro Roque Marques wrote: Radomir, An extra issue that i don't believe you've covered so far is about comment ownership. I've just read an email on the list that follows a pattern that i've heard many complaints about: -1 with a reasonable comment, submitter addresses the comment, reviewer never comes back. Reviewers do need to allocate time to come back and follow up on the answers to their comments. Perhaps there is an issue with the incentive system. You can earn karma by doing a code review... certainly you want to incentivise developers that help the project by improving the code quality. But if the incentive system allows for drive by shooting code reviews that can be a problem. It's not really an incentive system problem, this is some place where there are some gerrit limitations (especially when your list of reviewed code is long). Hopefully once we get a gerrit upgrade we can dashboard out some new items like that via the new rest API. I agree that reviewers could be doing better. But definitely also realize that part of this is just that there is *so* much code to review. Realize that most core reviewers aren't ignoring or failing to come back on patches intentionally. There is just *so* much of it. I feel guilty all the time by how big a review queue I have, but I also need a few hours a day not doing OpenStack (incredible to believe). This is where non core reviewers can really help in addressing the first couple of rounds of review to prune and improve the easy stuff. We're all in this together, -Sean -- Sean Dague http://dague.net signature.asc Description: OpenPGP digital signature ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] nova-api fails to start
It was a new installation, but i tried a couple more times, removed all the
component folders and it worked
--
___
Telles Mota Vidal Nóbrega
Undergraduated in Computer Science at Federal University of Campina Grande
(UFCG)
Developer at PulsarOpenStack Project - HP
On 07 Nov 2013, at 17:54, Krishanu Dhar rony.k...@gmail.com wrote:
Hey Telies - Were you trying to recreate the failure? or is it a new
installation?
On Fri, Nov 8, 2013 at 2:13 AM, Telles Nobrega tellesnobr...@gmail.com
wrote:
Now i have something like your problem, im getting
die 609 'nova-api did not start'
On Thu, Nov 7, 2013 at 4:11 PM, Krishanu Dhar rony.k...@gmail.com wrote:
thanks man, incidentally i ran into your post too and it got me going.
However, I was wondering if the fix should go in stack.sh.stack.sh
On Fri, Nov 8, 2013 at 12:32 AM, Cazzolato, Sergio J
sergio.j.cazzol...@intel.com wrote:
Hi, I had the same issue and fixed that doing a chwon and changing the
ownership to my user of the files in /etc/nova where the owner was the user
nova.
In my case the files were: api-paste.ini and policy.json
I posted the solution there too:
http://stackoverflow.com/questions/19843239/getting-nova628die-trying-to-start-openstack-nova-module
Thanks
From: Krishanu Dhar [mailto:rony.k...@gmail.com]
Sent: Thursday, November 07, 2013 3:40 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] nova-api fails to start
Any other recommendations on how to have a successful devstack installation?
On Thu, Nov 7, 2013 at 11:37 PM, Krishanu Dhar rony.k...@gmail.com wrote:
below is an error that's probably the cause...
2013-11-07 23:24:14.758 TRACE nova IOError: [Errno 13] Permission denied:
'/etc/nova/api-paste.ini'
2013-11-07 23:24:14.758 TRACE nova
n-api failed to start
krish@krish-VirtualBox:/opt/stack/nova$ ls -l /etc/nova/api-paste.ini
-rw--- 1 nova nova 4260 Apr 23 2013 /etc/nova/api-paste.ini
isn't it expected to fail if the file is owned by nova... weird.
On Thu, Nov 7, 2013 at 11:18 PM, Krishanu Dhar rony.k...@gmail.com wrote:
it did not even start the process in my case.
I tried looking up email threads in google and looks like quite a few have
run into this before, but couldn't find a working fix.
On Thu, Nov 7, 2013 at 11:15 PM, Telles Nobrega tellesnobr...@gmail.com
wrote:
Weird, i had the same problem, but when i kill the processes it works
On Thu, Nov 7, 2013 at 2:34 PM, Krishanu Dhar rony.k...@gmail.com wrote:
Nothing was left behind.
#ps aux|grep -ie nova did not return anything.
On Thu, Nov 7, 2013 at 11:01 PM, Telles Nobrega tellesnobr...@gmail.com
wrote:
Did you check if there are any nova process left running?
On Thu, Nov 7, 2013 at 2:28 PM, Krishanu Dhar rony.k...@gmail.com wrote:
Appreciate the responses. But there is something wrong with this. I ran
unstack.sh again and retried the installation. it failed with the same
message.
So, what are my options right now?
On Thu, Nov 7, 2013 at 7:31 PM, Telles Nobrega tellesnobr...@gmail.com
wrote:
Sometimes after ./unstack is ran, some process are still runnning for nova.
Try running this to kill them all (ps aux | grep -ie nova | awk '{print $2}'
| xargs kill -9) and try ./stack again
On Thu, Nov 7, 2013 at 9:14 AM, Noorul Islam K M noo...@noorul.com wrote:
Krishanu Dhar rony.k...@gmail.com writes:
Hi,
I was trying to install the devstack and it failed while starting the nova
api. below is a snippet from the console. Is it a bug?
+ screen -S stack -p n-api -X stuff 'cd /opt/stack/nova
/usr/local/bin/nova-a'i || echo n-api failed to start | tee
/opt/stack/status/stack/n-api.failure
+ echo 'Waiting for nova-api to start...'
Waiting for nova-api to start...
+ wait_for_service 60 http://10.0.2.15:8774
+ local timeout=60
+ local url=http://10.0.2.15:8774
+ timeout 60 sh -c 'while ! curl --noproxy '\''*'\'' -s
http://10.0.2.15:8774 /dev/null; do sleep 1; done'
+ die 628 'nova-api did not start'
+ local exitcode=0
+ set +o xtrace
[Call Trace]
./stack.sh:1084:start_nova_api
/home/krish/devstack/lib/nova:628:die
[ERROR] /home/krish/devstack/lib/nova:628 nova-api did not start
krish@krish-VirtualBox:~/devstack$
Did you try screen -x stack ?
Regards,
Noorul
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
--
Telles Mota Vidal Nobrega
Developer at PulsarOpenStack Project - HP/LSD-UFCG
--
Krishanu
--
--
Telles Mota Vidal Nobrega
Developer at PulsarOpenStack Project - HP/LSD-UFCG
[openstack-dev] [nova][api] Is this a potential issue
Hi, all I'm a bit confused of followed code in ./compute/api.py, which will be invoked by api/openstack/compute/servers.py, _action_revert_resize(). From the code seems there is a small windows between get the migration object and update migration.status. If another API request comes at this small window, it means two utility will try to revert resize at same time. Is this a potential issue? Currently implementation already roll back the reservation if something wrong, but not sure if we should update state to reverting as a transaction in get_by_instance_and_status()? --jyh def revert_resize(self, context, instance): Reverts a resize, deleting the 'new' instance in the process. elevated = context.elevated() migration = migration_obj.Migration.get_by_instance_and_status( elevated, instance.uuid, 'finished') Here we get the migration object # reverse quota reservation for increased resource usage deltas = self._reverse_upsize_quota_delta(context, migration) reservations = self._reserve_quota_delta(context, deltas) instance.task_state = task_states.RESIZE_REVERTING instance.save(expected_task_state=None) migration.status = 'reverting' Here we update the status. migration.save() ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Bad review patterns
On 11/07/2013 07:54 PM, Sean Dague wrote: On 11/08/2013 01:37 AM, Pedro Roque Marques wrote: Radomir, An extra issue that i don't believe you've covered so far is about comment ownership. I've just read an email on the list that follows a pattern that i've heard many complaints about: -1 with a reasonable comment, submitter addresses the comment, reviewer never comes back. Reviewers do need to allocate time to come back and follow up on the answers to their comments. Perhaps there is an issue with the incentive system. You can earn karma by doing a code review... certainly you want to incentivise developers that help the project by improving the code quality. But if the incentive system allows for drive by shooting code reviews that can be a problem. It's not really an incentive system problem, this is some place where there are some gerrit limitations (especially when your list of reviewed code is long). Hopefully once we get a gerrit upgrade we can dashboard out some new items like that via the new rest API. I agree that reviewers could be doing better. But definitely also realize that part of this is just that there is *so* much code to review. Realize that most core reviewers aren't ignoring or failing to come back on patches intentionally. There is just *so* much of it. I feel guilty all the time by how big a review queue I have, but I also need a few hours a day not doing OpenStack (incredible to believe). This is where non core reviewers can really help in addressing the first couple of rounds of review to prune and improve the easy stuff. We're all in this together, Is there a way for Gerrit to only send email when action is required, rather than on any change to any review you've touched? If Gerrit sent less mail, it would be easier to treat its mails as a critical call to action to re-review. (There's probably a way to use fancy message filtering to accomplish this, but that would only work for people willing/able to set up such filtering.) -- David Ripton Red Hat drip...@redhat.com ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Solum] Some initial code copying for db/migration
- Original Message - https://github.com/openstack/nova/blob/master/nova/db/sqlalchemy/api.py#L420 https://github.com/openstack/nova/blob/master/nova/db/sqlalchemy/models.py#L43 This API and these models are what we are trying to avoid exposing to the rest of nova. By wrapping these in our NovaObject-based structures, we can bundle versioned data and methods together which is what we need for cross-version compatibility and parity for the parts of nova that are not allowed to talk to the database directly. See the code in nova/objects/* for the implementations. Right now, these just call into the db_api.py, but eventually we want to move the actual database implementation into the objects themselves and hopefully dispense with most or all of the sqlalchemy/* stuff. This also provides us the ability to use other persistence backends that aren't supported by sqlalchemy, or that don't behave like it does. If you're going to be at the summit, come to the objects session on Thursday where we'll talk about this in more detail. Other projects have expressed interest in moving the core framework into Oslo so that we're all doing things in roughly the same way. It would be good to get you started on the right way early on before you have the migration hassle we're currently enjoying in Nova :) --Dan The summit session was excellent - next step for me is to look through what the right abstraction is going to be for objects that keeps the db details properly isolated and the API surface on /objects suitably coarse (in line with the long discussion in Nova about non-SQL backends, the consensus of which is that the domain object model needs to abstract whole interaction flows, vs granular steps). I'll try to have some example code to debate after I get back from summit. Even assuming Solum has a fairly small persistence model, in the long run I believe it's fair to say that the ability to perform live upgrades will become critical for all operators. One of the side effects of supporting potentially millions of applications (at the high end, and not an unreasonable estimate for hosted environments) is that any period of downtime at the API level will prevent users from making deployments, which is a direct line-of-business concern. Designing around live upgrades - specifically, the requirement that code must be aware of two versions of a schema at the same time - implies that the domain model must be able to be aware of those versions on an object basis. For reference, [1] and [2] contain some of the Nova discussion, and Nova in icehouse is going to be moving this way. I'd prefer (it's important to Red Hat) to design for that from the beginning and be working towards that end. Do folks have additional questions or concerns about my exploration of a versioned domain object model from day one? Are there others who would like to embrace quick and dirty and explicitly ignore this issue until we have a Solum prototype running? [1] https://etherpad.openstack.org/p/NovaIcehouseSummitUpgrades [2] https://etherpad.openstack.org/p/NovaIcehouseSummitObjects ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] Shall backward compatibility env. vars be removed from python-clients?
Hi all, Clients like python-novaclient/cinderclient/trove still support NOVA_*, CINDER_*, TROVE_* variables for backward compatibility support,while clients like python-neutronclient/keystoneclient only supports OS_* env vars. The following bug (#1061491, see review), mentions that it may be confusing if novaclient for instance, silently accept those variables without even being mentioned on the current help/documentation neither warning the user at all. (User has exported NOVA_USERNAME/CINDER_USERNAME/etc instead of OS_USERNAME etc.) As Kevin suggested on the review, (https://review.openstack.org/#/c/55588/) “we need to make sure that we have consensus that enough time has passed to drop the old variables”. I would like to hear opinions about this. Some options that i can think of are: 1) Remove NOVA_USERNAME, NOVA_PASSWORD and NOVA_PROJECT_ID support from novaclient. Same for other clients allowing vars other than OS_USERNAME, OS_PASSWORD, OS_TENANT_ID for this specific options. 2) Warn about deprecation if they are being used. 3) Ignore this topic, keep everything as today and just close the 'bug/suggestion'. 4) Other? Best Regards -Leandro PS: shall this message belong to another ML, please, let me know. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] IPv6 sub-team?
How about scheduling an IRC meeting in close proximity to the other Neutron meetings on Mondays? * 20:00 to 21:00 UTC, before the Neutron meeting OR * 23:00 UTC - after the distributed virtual router meeting? -- Sean M. Collins ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] What key strings can we set in scheduler_hints param when boot an instance?
The hints are coded into the various scheduler filters, so the set supported on any install depends on what filters have been configured. I have a change under way (I need to just find the time to go back and fix the last wave of review comments) to expose what is supported via an API call https://review.openstack.org/#/c/34291/ From: openstack learner [mailto:openstacklea...@gmail.com] Sent: 06 November 2013 20:01 To: openstack-dev@lists.openstack.org; openst...@lists.openstack.org Subject: [openstack-dev] What key strings can we set in scheduler_hints param when boot an instance? Hi all, I am using the nova python api and recently i need to use the filter schedule hint when i boot up an instance. In the novaclient.v1_1.client.Client.servers.create() method, there is a :param scheduler_hints: (optional extension) arbitrary key-value pairs specified by the client to help boot an instance which we can specify the key-value pairs to help boot an instance. However, i don't know what key string can I specify in my key-values pairs. I search online but did not get any information about that? Is there any document that list all the keystrings we can specify in the scheduler_hints? I would like to have a list of all the keys that we can specify in the scheduler_hints. Thanks a lot xin ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] Climate Project Slides
Guys, there was presentation about Climate Project (Reservation Service for OpenStack) on this Hong Kong Summit. Please take a look on Slideshare slides if you are interested in it: Climate project slideshttp://www.slideshare.net/dbelova/climate-project-28026918 Thank everybody who have come on our session! Best regards, Dina Belova Software Engineer Mirantis Inc. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Nova] [Climate] Reservation service called Climate
Guys, there are Slideshare slides if it is more comfortable to use them for you: Slideshare Climate Slideshttp://www.slideshare.net/dbelova/climate-project-28026918 Thanks! On Wed, Nov 6, 2013 at 5:47 PM, Sylvain Bauza sylvain.ba...@bull.netwrote: Hi, During the Design session https://etherpad.openstack.org/p/NovaIcehouse-Instance-Group-API we discussed the fact that this is not the role of Nova for doing atomic reservations in order to ensure the user needs will be met. I raised the point (and sorry for my bad accent, was stressy) that we're already trying to provide a reservation system for Openstack, called Climate (a Stackforge project). I would really like to discuss with you all, Nova community, about the reservation system and ensure that we, at Climate, are on the good path. Climate is planning to reserve both virtual instances and physical hosts, but for the discussion we had, only physical hosts usecase is relevant. We had an unconference session today at 2pm, I can share you the slides : https://docs.google.com/presentation/d/1BJGmtzGees6tg_Np7JuKFtuLGiCaguVYD8hYJ2eVKAc/edit#slide=id.p (please focus on slides 11-14, they're talking on the design for host reservations) All the code is located on Stackforge, but please note the most important part of physical host reservations is still under review there : https://review.openstack.org/#/q/project:+stackforge/climate+status:open,n,z (We're missing reviewers, by the way !) I'm open to discuss and waiting your thoughts, -Sylvain ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Best regards, Dina Belova Software Engineer Mirantis Inc. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Heat] How do i implement this usecase:
On 11/07/2013 06:42 PM, Simon Pasquier wrote:
Hi,
The OS::Neutron::FloatingIP resource works in the same manner as the
'neutron floating-create' command so currently there is no way to
avoid passing the floating network id. The AWS::EC2::EIP resource
doesn't require it because it uses the Nova API to allocate floating
IPs. In turn, Nova API knowns the floating network with the
default_floating_pool parameter defined in your nova.conf file.
I guess what you are looking for is a OS::Nova::FloatingIP resource.
As a workaround, you could leverage environments [1] and map to the
EC2 EIP resource:
resource_registry:
OS::Nova::FloatingIP: AWS::EC2::EIP
Simon
[1]
http://docs.openstack.org/developer/heat/template_guide/environment.html
I had assumed that nova-networking was sufficiently deprecated that it
is not worth writing native heat resources for things like floating-ip.
I certainly won't be working on them but I currently have no problem
with some blueprints being raised and these resources being contributed.
Le 07/11/2013 09:33, Nilakhya a écrit :
Currently my heat template works with AWS resource type:
DatabaseIPAddress:
Type: AWS::EC2::EIP
DatabaseIPAssoc :
Type: AWS::EC2::EIPAssociation
Properties:
InstanceId: {Ref: BaseInstance}
EIP: {Ref: MyIPAddress}
Now if i want to change to OpenStack ( OS ) namespace with a similar
implementation :
MyIPAddress:
Type: OS::Neutron::FloatingIP
Properties:
floating_network_id : String
MyIPAssoc :
Type: OS::Neutron::FloatingIPAssociation
Properties:
floatingip_id : {Ref: MyIPAddress}
I cannot problem is,
a) floating_network_id ( is not known ) which is a required property.
b) Even if its available / defaults to, its an overhead from AWS
simplicity.
As an aside, you only need to use OS::Neutron::FloatingIPAssociation if
the floating IP reference is passed in as a template parameter. If it is
all in a self-contained template, just do the association with
OS::Neutron::FloatingIP.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Swift] log line length
Hi Alex, It seems that this is likely an rsyslog limit, so you might want to check out: http://www.rsyslog.com/doc/rsyslog_conf_global.html Specifically, the info on $MaxMessageSize Regards, -peter On Thu, Nov 7, 2013 at 5:42 PM, Pecoraro, Alex alex.pecor...@emc.com wrote: Is there any way for me to change the logging so that it doesn’t truncate the output – so basically the length of the line printed to the log is not limited to a certain length? Thanks. Alex ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [sqlalchemy-migrate] Blueprint for review: Add DB2 10.5 Support
With OpenStacks test and gating oriented mindset, how can we gate on this functionality working going forward? On Fri, Nov 1, 2013 at 3:30 AM, Matt Riedemann mrie...@us.ibm.com wrote: I've got a sqlalchemy-migrate blueprint up for review to add DB2 support in migrate. *https://blueprints.launchpad.net/sqlalchemy-migrate/+spec/add-db2-support*https://blueprints.launchpad.net/sqlalchemy-migrate/+spec/add-db2-support This is a pre-req for getting DB2 support into Nova so I'm targeting icehouse-1. We've been running with the migrate patches internally since Folsom, but getting them into migrate was difficult before OpenStack took over maintenance of the project. Please let me know if there are any questions/issues or something I need to address here. Thanks, Matt Riedemann Cloud Solutions and OpenStack Development Email: mrie...@us.ibm.com Office Phone: 507-253-7622 ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Solum] Choice of API infrastructure
On Fri, Nov 8, 2013 at 8:02 AM, Jay Pipes jaypi...@gmail.com wrote: On 11/07/2013 06:41 PM, Adrian Otto wrote: Solum Team, First of all I wanted to say that I have been thinking a lot about this thread, and have been seeking input from a number of you who attended the Summit this week. I do *not* see this decision as a critical one, because if something really mattered a ton we could rip our one framework and put another in. What I love about this discussion is that we are having a healthy debate about different points of view, which was very thought provoking. I have heard input from skeptics who think that engineering decisions have to be made in a small group in order to be efficient. I know that thinking is wrong, and it's examples like these that convince me further that discussions like these help us make better choices, and make development more efficient over the long run. We should give the most weight to the preferences of the engineers who will write and maintain the code. If there are team members who are volunteering to write and maintain the bulk of our API code over a period of time who really want Falcon over Pecan, then we should give that fair consideration. The API is exceedingly important to Solum, and all of us will be working on it, so we need a choice that all of us can live with. I suggest that we settle on Pecan+WSME, for the following reasons: 1) It is a known quantity, and is likely to work well for Solum's needs, considering that Solum is primarily a control plane API system, and that performance is not a primary motivator. 2) Pecan+WSME allows us to offer data serializations in both JSON and XML to help satisfy the preferences of the API consumers. 3) It allows us to have multiple models that are loosely coupled, which can aid in data validation. 4) At this point in time, other OpenStack core/integrated/ecosystem projects are using Pecan+WSME, and several Solum contributors will be switching between projects. There is an advantage to a higher level of consistency among various projects. I accept that Webob may be problematic for us, that performance may be less than ideal, and that some Solum developers may dislike working with WSME, and that Falcon may actually be more pleasant to work with. We have team members with a deep understanding of Falcon, and could definitely make it work. We can proceed with Pecan+WSME accepting these (and other) trade-offs. Are there any other critically important considerations that we should consider before converging on this choice? I'd like to hear that input prior to our next IRC meeting. None that I can think of. I'll get behind the decision, then, and if all are in consensus, I'll abandon the Falcon API patch. We do need to get the Pecan/WSME patch to pass the gates though :) Doug, I'm hoping you might give Noorul a hand with that next week upon your return from Hong Kong? I'd be happy to help. Please add me as a reviewer on the patch set if I'm not already listed. Doug All the best, -jay ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] L3 advanced features blueprint mapping to IETF and IEEE standards
What about an IRC meeting on this topic 11/19 at 9 p.m. PST ? This is 2 p.m in Japan and 6 a.m CET on the 20th. It is not ideal but i suspect we will have interest in participating from both Europe and Asia. I volunteer myself and Nachi Ueno na...@ntti3.com (the author of the BGP MPLS blueprint) as agenda organizers; please drop us a note if you intend to attend and wether you would like to present something to the group. Pedro. On Nov 7, 2013, at 11:27 AM, Rochelle.Grober rochelle.gro...@huawei.com wrote: From: Pedro Roque Marques [mailto:pedro.r.marq...@gmail.com] Colin, The nice thing about standards is that there are so many of them to choose from. For instance, if you take this Internet Draft: http://tools.ietf.org/html/draft-ietf-l3vpn-end-system-02 which is based on RFC4364. It has already been implemented as a Neutron plugin via OpenContrail (http://juniper.github.io/contrail-vnc/README.html); With this implementation each OpenStack cluster can be configured as its own Autonomous System. There is a blueprint https://blueprints.launchpad.net/neutron/+spec/neutron-bgp-mpls-vpn that is discussing adding the provisioning of the autonomous system and peering to Neutron. Please note that the work above does interoperate with 4364 using option B. Option C is possible but not that practical (as an operator you probably don't want to expose your internal topology between clusters). If you want to give it a try you can use this devstack fork: https://github.com/dsetia/devstack. You can use it to interoperate with a standard router that implements 4364 and support MPLS over GRE. Products from cisco/juniper/ALU/huwawei etc do. I believe that the work i'm referencing implements interoperability while having very minimal changes to Neutron. It is based on the same concept of neutron virtual network and it hides the BGP/MPLS functionality from the user by translating policies that establish connectivity between virtual networks into RFC 4364 concepts. Please refer to: https://blueprints.launchpad.net/neutron/+spec/policy-extensions-for-neutron Would it make sense to have an IRC/Web meeting around interoperability with RFC4364 an OpenStack managed clusters ? I believe that there is a lot of work that has already been done there by multiple vendors as well as some carriers. +1 And it should be scheduled and announced a reasonable time in advance developers can plan to participate. --Rocky Pedro. On Nov 7, 2013, at 12:35 AM, Colin McNamara co...@2cups.com wrote: I have a couple concerns that I don’t feel I clearly communicated during the L3 advanced features session. I’d like to take this opportunity to both clearly communicate my thoughts, as well as start a discussion around them. Building to the edge of the autonomous system The current state of neutron implementation is functionally the l2 domain and simple l3 services that are part of a larger autonomous system. The routers and switches northbound of the OpenStack networking layer handled the abstraction and integration of the components. Note, I use the term “Autonomous System” to describe more then the notion of BGP AS, but more broadly in the term of a system that is controlled within a common framework and methodology, and integrates with a peer system that doesn’t not share that same scope or method of control These components that composed the autonomous system boundary implement protocols and standards that map into IETF and IEEE standards. The reasoning for this is interoperability. Before vendors utilize IETF for interoperability at this layer, the provider experience was horrible (this was my personal experience in the late 90’s). Wednesdays discussions in the Neutron Design Sessions A couple of the discussions, most notably the extension of l3 functionality fell within the scope of starting the process of extending Neutron with functionality that will result (eventually) in the ability for an OpenStack installation to operate as it’s own Autonomous System. The discussions that occurred to support L3 advanced functionality (northbound boundary), and the QOS extension functionality both fell into the scope of Northbound and Southbound boundaries of this system. My comments in the session My comments in the session, while clouded with jet-lag were specifically around two concepts that are used when integrating other types of systems 1. In a simple (1-8) tenant environment integration with a northbound AS is normally done in a PE-CE model that generally centers around mapping dot1q tags into the appropriate northbound l3 segments and then handling the availability of the L2 path that traverses with port channeling, MLAG, STP, Etc. 2. In a complex environment (8+ for discussion) different Carrier Supporting Carrier (CSC) methods defined in IETF RFC 4364 Section 10 type A, B or C are
[openstack-dev] [TripleO] Contributing hardware to the TripleO CD cloud
Hi, over this week a number of organisations have expressed interest in contributing to the TripleO CD cloud, to help OpenStack bare metal testing, and testing of things that cannot run in nested environments - some hypervisors, savannah etc. I've drawn up a draft of whats involved in such a contribution - https://wiki.openstack.org/wiki/TripleO/TripleOCloud/Regions#Contributing_a_region_to_the_TripleOCloud - it's subject to review based on your feedback etc, but I'm pretty excited by this. Please contact me (off-list (rbtcoll...@hp.com) or on-list - up to you) if you're interested in contributing a region. We're not sure how large the cloud needs to be to test everything that we need to test, but we are sure that it's not big enough yet - testing just the gate for bare metal deployed KVM clouds would have required 80 machines during the H release period : 20 patches landing per hour, but re-tests when things failed in the gate means more like 40 runs per hour, 2 machines per run, an hour budget for bare metal deployed runs. Cheers, Rob -- Robert Collins rbtcoll...@hp.com Distinguished Technologist HP Converged Cloud ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [OpenStack-Infra] Stackforge projects: integration launchpad with openstack gerrit.
Thanks, I have another question. For some reasons openstack-bot don't update bugs in fuel project. E.g. we have a bug https://bugs.launchpad.net/fuel/+bug/1248876 And a patch with https://review.openstack.org/#/c/55527/ with message Closes-bug: 1248876 Bot didn't change status of the bug after this patch was merged. I read Project Group Managementhttps://wiki.openstack.org/wiki/Project_Group_Management#Launchpad article and added hudson-openstack to fuel-bugs team https://launchpad.net/~fuel-bugs But it didn't help. Thanks. On Fri, Nov 1, 2013 at 9:34 PM, Sergey Lukjanov slukja...@mirantis.comwrote: Hi, you should add your project at Launchpad to the ‘openstack’ project group and it’ll work ok. You can do it at https://launchpad.net/fuel/+edit and prop. “Part of Sincerely yours, Sergey Lukjanov Savanna Technical Lead Mirantis Inc. On Nov 1, 2013, at 1:56 AM, Evgeniy L e...@mirantis.com wrote: Hi, We have several projects in stackforge: https://github.com/stackforge/fuel-web https://github.com/stackforge/fuel-ostf https://github.com/stackforge/fuel-main https://github.com/stackforge/fuel-astute Also we have a project in launchpad https://launchpad.net/fuel For example we made a patch https://review.openstack.org/#/c/54535/ This patch contains special keyword blueprint fix-flake8-in-nailgun-repo, and gerrit made it as a link but there is wrong href https://blueprints.launchpad.net/openstack/?searchtext=fix-flake8-in-nailgun-repo This is link on openstack project in launchpad, *not fuel *project. So it should look like https://blueprints.launchpad.net/fuel/?searchtext=fix-flake8-in-nailgun-repo I think we have misconfiguration. My question is: how can we fix it? Thanks. ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] Stackforge projects: integration launchpad with openstack gerrit.
Evgeniy, The notation 'Fixes bug #1234567' or 'Fixes: bug #1234567' works for us. For example: https://bugs.launchpad.net/savanna/+bug/1223953 Possibly the bot does not recognize 'Closes-bug: #1234567' Dmitry 2013/11/7 Evgeniy L e...@mirantis.com Thanks, I have another question. For some reasons openstack-bot don't update bugs in fuel project. E.g. we have a bug https://bugs.launchpad.net/fuel/+bug/1248876 And a patch with https://review.openstack.org/#/c/55527/ with message Closes-bug: 1248876 Bot didn't change status of the bug after this patch was merged. I read Project Group Managementhttps://wiki.openstack.org/wiki/Project_Group_Management#Launchpad article and added hudson-openstack to fuel-bugs team https://launchpad.net/~fuel-bugs But it didn't help. Thanks. On Fri, Nov 1, 2013 at 9:34 PM, Sergey Lukjanov slukja...@mirantis.comwrote: Hi, you should add your project at Launchpad to the ‘openstack’ project group and it’ll work ok. You can do it at https://launchpad.net/fuel/+edit and prop. “Part of Sincerely yours, Sergey Lukjanov Savanna Technical Lead Mirantis Inc. On Nov 1, 2013, at 1:56 AM, Evgeniy L e...@mirantis.com wrote: Hi, We have several projects in stackforge: https://github.com/stackforge/fuel-web https://github.com/stackforge/fuel-ostf https://github.com/stackforge/fuel-main https://github.com/stackforge/fuel-astute Also we have a project in launchpad https://launchpad.net/fuel For example we made a patch https://review.openstack.org/#/c/54535/ This patch contains special keyword blueprint fix-flake8-in-nailgun-repo, and gerrit made it as a link but there is wrong href https://blueprints.launchpad.net/openstack/?searchtext=fix-flake8-in-nailgun-repo This is link on openstack project in launchpad, *not fuel *project. So it should look like https://blueprints.launchpad.net/fuel/?searchtext=fix-flake8-in-nailgun-repo I think we have misconfiguration. My question is: how can we fix it? Thanks. ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] Stackforge projects: integration launchpad with openstack gerrit.
Dmitry, We tried but it didn't help. https://review.openstack.org/#/c/2/ https://bugs.launchpad.net/fuel/+bug/1248960 On Thu, Nov 7, 2013 at 4:39 PM, Dmitry Mescheryakov dmescherya...@mirantis.com wrote: Evgeniy, The notation 'Fixes bug #1234567' or 'Fixes: bug #1234567' works for us. For example: https://bugs.launchpad.net/savanna/+bug/1223953 Possibly the bot does not recognize 'Closes-bug: #1234567' Dmitry 2013/11/7 Evgeniy L e...@mirantis.com Thanks, I have another question. For some reasons openstack-bot don't update bugs in fuel project. E.g. we have a bug https://bugs.launchpad.net/fuel/+bug/1248876 And a patch with https://review.openstack.org/#/c/55527/ with message Closes-bug: 1248876 Bot didn't change status of the bug after this patch was merged. I read Project Group Managementhttps://wiki.openstack.org/wiki/Project_Group_Management#Launchpad article and added hudson-openstack to fuel-bugs team https://launchpad.net/~fuel-bugs But it didn't help. Thanks. On Fri, Nov 1, 2013 at 9:34 PM, Sergey Lukjanov slukja...@mirantis.comwrote: Hi, you should add your project at Launchpad to the ‘openstack’ project group and it’ll work ok. You can do it at https://launchpad.net/fuel/+edit and prop. “Part of Sincerely yours, Sergey Lukjanov Savanna Technical Lead Mirantis Inc. On Nov 1, 2013, at 1:56 AM, Evgeniy L e...@mirantis.com wrote: Hi, We have several projects in stackforge: https://github.com/stackforge/fuel-web https://github.com/stackforge/fuel-ostf https://github.com/stackforge/fuel-main https://github.com/stackforge/fuel-astute Also we have a project in launchpad https://launchpad.net/fuel For example we made a patch https://review.openstack.org/#/c/54535/ This patch contains special keyword blueprint fix-flake8-in-nailgun-repo, and gerrit made it as a link but there is wrong href https://blueprints.launchpad.net/openstack/?searchtext=fix-flake8-in-nailgun-repo This is link on openstack project in launchpad, *not fuel *project. So it should look like https://blueprints.launchpad.net/fuel/?searchtext=fix-flake8-in-nailgun-repo I think we have misconfiguration. My question is: how can we fix it? Thanks. ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] Stackforge projects: integration launchpad with openstack gerrit.
Evgeniy L wrote: Dmitry, We tried but it didn't help. https://review.openstack.org/#/c/2/ https://bugs.launchpad.net/fuel/+bug/1248960 You might need to update the mapping between the LP project name and the git repo names. See at: https://github.com/openstack-infra/jeepyb/blob/master/jeepyb/projects.py#L134 -- Thierry Carrez (ttx) ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
[Openstack] kvm troubleshooting
Hi installing nova it says kvm wasn't installed on my controller, message which saw for the first time when I try to inqtall kvm it says packages doesn't exist any help will be welcome -- Stéphane EVEILLARD Responsable Système et Développement IBS NETWORK Coordinateur Version Française Openstack ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Re: [Openstack] [Neutron] Security groups issue when running latest libvirt?
Le 07/11/2013 03:18, Martinx - ジェームズ a écrit :
That is true... Back to LibvirtHybridOVSBridgeDriver, Security Groups
is working again...
Thanks for the feedback Thiago. I've opened a bug on Launchpad:
https://bugs.launchpad.net/nova/+bug/1248859
On 6 November 2013 15:03, Simon Pasquier simon.pasqu...@bull.net
mailto:simon.pasqu...@bull.net wrote:
Answering myself as I investigated a little further and
cross-posting to openstack-dev because I'd like to get feedback from
Nova/Neutron devs.
Users running Havana should configure
libvirt_vif_driver=nova.virt.__libvirt.vif.__LibvirtHybridOVSBridgeDriver.
This driver is still available in the Havana release although
deprecated. AFAIU, this is the only option if you want effective
security groups with KVM OVS.
For people using the master branch of nova, sorry but security
groups are currently broken because LibvirtHybridOVSBridgeDriver is
gone ([0]). Joe Gordon asked the Neutron devs about it few weeks ago
[1] but no answer and in another review [2], the conclusion was that
the Tempest tests passed with Neutron. However I don't see anywhere
in the tests ([3], [4]) that we check if the security rules
allow/block traffic.
It would be nice if core devs could confirm or refute.
Regards,
Simon
[0] https://review.openstack.org/#__/c/49660/
https://review.openstack.org/#/c/49660/
[1]
http://lists.openstack.org/__pipermail/openstack-dev/2013-__October/016886.html
http://lists.openstack.org/pipermail/openstack-dev/2013-October/016886.html
[2] https://review.openstack.org/#__/c/44349
https://review.openstack.org/#/c/44349
[3]
https://github.com/openstack/__tempest/blob/master/tempest/__api/network/test_security___groups.py
https://github.com/openstack/tempest/blob/master/tempest/api/network/test_security_groups.py
[4]
https://github.com/openstack/__tempest/blob/master/tempest/__api/network/test_security___groups_negative.py
https://github.com/openstack/tempest/blob/master/tempest/api/network/test_security_groups_negative.py
Le 05/11/2013 14:57, Simon Pasquier a écrit :
Hi all,
I'm struggling with security groups on Havana with Neutron and OVS
plugin (GRE tunnels). No problem to create/delete security group
rules
but even though iptables configuration is updated, traffic to my
instances is never filtered [0].
I'm running DevStack on 2 nodes (1 controller + 1 compute):
- OS: Ubuntu 12.04.3 (LTS) with the Havana cloud archive repository.
- Open vSwitch package version: 1.10.2-0ubuntu2~cloud0
- libvirt package version: 1.1.1-0ubuntu8~cloud2
- localrc, nova.conf, neutron.conf and ovs_neutron_plugin.ini files
pasted at [1] (I didn't modify any of these files after the
DevStack run)
According to [2], [3] and [4], iptables is not compatible with TAP
devices connectd directly to Open vSwitch ports, this is why
there used
to be the additional veth + bridge interfaces [5]. But in my
setup, this
is not the case anymore as shown in [6] ('ovs-vsctl show' +
'iptables-save' ouptut). I've also pasted the libvirt XML
configuration
[7] that shows that the instance is directly connected to the
Open vSwitch.
Are the security groups supposed to work when the instance is
directly
connected to OVS? If yes, what am I doing wrong?
Regards,
[0] http://paste.openstack.org/__show/50490/
http://paste.openstack.org/show/50490/
[1] http://paste.openstack.org/__show/50448/
http://paste.openstack.org/show/50448/
[2]
http://www.spinics.net/linux/__fedora/libvirt-users/msg05384.__html
http://www.spinics.net/linux/fedora/libvirt-users/msg05384.html
[3]
http://openvswitch.org/__pipermail/discuss/2013-__October/011461.html
http://openvswitch.org/pipermail/discuss/2013-October/011461.html
[4]
http://docs.openstack.org/__havana/config-reference/__content/under_the_hood___openvswitch.html
http://docs.openstack.org/havana/config-reference/content/under_the_hood_openvswitch.html
[5]
http://docs.openstack.org/__havana/config-reference/__content/figures/7/a/a/common/__figures/under-the-hood-__scenario-2-ovs-compute.png
http://docs.openstack.org/havana/config-reference/content/figures/7/a/a/common/figures/under-the-hood-scenario-2-ovs-compute.png
[6] http://paste.openstack.org/__show/50486/
http://paste.openstack.org/show/50486/
[7] http://paste.openstack.org/__show/50487/
http://paste.openstack.org/show/50487/
--
Simon Pasquier
Software Engineer
Bull, Architect of an Open World
Phone: + 33 4 76 29 71 49 tel:%2B%2033%204%2076%2029%2071%2049
http://www.bull.com
Re: [Openstack] kvm troubleshooting
Hello stephane, Which operating system do you use Regards, Ritesh On Thu, Nov 7, 2013 at 1:58 PM, Stephane EVEILLARD stephane.eveill...@gmail.com wrote: Hi installing nova it says kvm wasn't installed on my controller, message which saw for the first time when I try to inqtall kvm it says packages doesn't exist any help will be welcome -- Stéphane EVEILLARD Responsable Système et Développement IBS NETWORK Coordinateur Version Française Openstack ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack -- * With Regards * * Ritesh Nanda* http://www.ericsson.com/ ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Re: [Openstack] Is there any way to extend the ip address of subnet?
Hi Sam, Unfortunately we do not support updating the allocation-pools on subnets at this time. This is something that we should definitely fix though in neutron. Aaron On Wed, Nov 6, 2013 at 10:46 PM, Sam Lee lixq2...@gmail.com wrote: Hi All, I have created a subnet with 10 ips. But now I need more than ten instances, is there any way to extend the subnet to add ip address? eg: I have ten ips as following: 172.16.2.210 ~ 172.16.2.220 I want to add 20 more ips, and so the result will be 172.16.2.210 ~ 172.16.2.230 I try subnet-update command and create a new subnet with the same CIDR, but it doesn't work correctly. Thanks in advance. ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Re: [Openstack] kvm troubleshooting
On Thu, Nov 7, 2013 at 9:28 AM, Stephane EVEILLARD stephane.eveill...@gmail.com wrote: Hi installing nova it says kvm wasn't installed on my controller, message which saw for the first time when I try to inqtall kvm it says packages doesn't exist Which operating system are you using? How are you installing nova? Can you post the exact command and output? On ubuntu, the package name you have to install is nova-compute-kvm which in turns will install kvm. However, you should first check if your machine supports kvm. The command to run is kvm-ok, and it belongs to the cpu-checker package. .a. -- antonio.s.mess...@gmail.com antonio.mess...@uzh.ch +41 (0)44 635 42 22 GC3: Grid Computing Competence Center http://www.gc3.uzh.ch/ University of Zurich Winterthurerstrasse 190 CH-8057 Zurich Switzerland ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Re: [Openstack] Havana Network node Doc
I can’t find the link to this page in the home doc page (http://docs.openstack.org/). Is it a bug? Giuliano Da: Aaron Rosen Data invio: mercoledì 6 novembre 2013 12.24 A: Jitendra Bhaskar Cc: openstack@lists.openstack.org http://docs.openstack.org/network-admin/admin/content/install_ubuntu.html On Wed, Nov 6, 2013 at 2:25 AM, Jitendra Bhaskar jeetuind...@gmail.com wrote: can we have any clear docs to setup network node. -- Thanks Regards Jitendra Kumar Bhaskar Cell:- +91 7306311531 :- +91 9989743042 ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Re: [Openstack] [Horizon] New instance creation failed
Hi Somanchi
I see error Tue Oct 29 11:17:20 2013] [error] ServiceCatalogException:
Invalid service catalog service: network.
You can try defining the 'keystone service-create' with type=Network(N is
uppercase). I was troubleshooting something with Nova-compute. After making
it upper case it started working fine.
-Dheerendra
On Tue, Oct 29, 2013 at 4:45 PM, Somanchi Trinath-B39208
b39...@freescale.com wrote:
Hi-
I have got the following error in apache error logs while I try to bring
up a new instance.
I have followed Openstack Havana for Ubuntu 12.04 LTS installation manual
from docs.openstack.org.
I’m going with single node (both controller and compute node on a single
machine) installation.
[Tue Oct 29 11:17:20 2013] [error] Problem instantiating action class.
[Tue Oct 29 11:17:20 2013] [error] Traceback (most recent call last):
[Tue Oct 29 11:17:20 2013] [error] File
/usr/lib/python2.7/dist-packages/horizon/workflows/base.py, line 376, in
action
[Tue Oct 29 11:17:20 2013] [error] context)
[Tue Oct 29 11:17:20 2013] [error] File
/usr/lib/python2.7/dist-packages/horizon/workflows/base.py, line 141, in
__init__
[Tue Oct 29 11:17:20 2013] [error] self._populate_choices(request,
context)
[Tue Oct 29 11:17:20 2013] [error] File
/usr/lib/python2.7/dist-packages/horizon/workflows/base.py, line 154, in
_populate_choices
[Tue Oct 29 11:17:20 2013] [error] bound_field.choices = meth(request,
context)
[Tue Oct 29 11:17:20 2013] [error] File
/usr/share/openstack-dashboard/openstack_dashboard/wsgi/../../openstack_dashboard/dashboards/project/instances/workflows/create_instance.py,
line 510, in populate_network_choices
[Tue Oct 29 11:17:20 2013] [error] _('Unable to retrieve networks.'))
[Tue Oct 29 11:17:20 2013] [error] File
/usr/share/openstack-dashboard/openstack_dashboard/wsgi/../../openstack_dashboard/dashboards/project/instances/workflows/create_instance.py,
line 503, in populate_network_choices
[Tue Oct 29 11:17:20 2013] [error] networks =
api.neutron.network_list_for_tenant(request, tenant_id)
[Tue Oct 29 11:17:20 2013] [error] File
/usr/share/openstack-dashboard/openstack_dashboard/wsgi/../../openstack_dashboard/api/neutron.py,
line 456, in network_list_for_tenant
[Tue Oct 29 11:17:20 2013] [error] shared=False, **params)
[Tue Oct 29 11:17:20 2013] [error] File
/usr/share/openstack-dashboard/openstack_dashboard/wsgi/../../openstack_dashboard/api/neutron.py,
line 434, in network_list
[Tue Oct 29 11:17:20 2013] [error] networks =
neutronclient(request).list_networks(**params).get('networks')
[Tue Oct 29 11:17:20 2013] [error] File
/usr/share/openstack-dashboard/openstack_dashboard/wsgi/../../openstack_dashboard/api/neutron.py,
line 423, in neutronclient
[Tue Oct 29 11:17:20 2013] [error] % (request.user.token.id,
base.url_for(request, 'network')))
[Tue Oct 29 11:17:20 2013] [error] File
/usr/share/openstack-dashboard/openstack_dashboard/wsgi/../../openstack_dashboard/api/base.py,
line 268, in url_for
[Tue Oct 29 11:17:20 2013] [error] raise
exceptions.ServiceCatalogException(service_type)
[Tue Oct 29 11:17:20 2013] [error] ServiceCatalogException: Invalid
service catalog service: network
[Tue Oct 29 11:17:20 2013] [error] Internal Server Error:
/horizon/project/instances/launch
[Tue Oct 29 11:17:20 2013] [error] Traceback (most recent call last):
[Tue Oct 29 11:17:20 2013] [error] File
/usr/lib/python2.7/dist-packages/django/core/handlers/base.py, line 140,
in get_response
[Tue Oct 29 11:17:20 2013] [error] response = response.render()
[Tue Oct 29 11:17:20 2013] [error] File
/usr/lib/python2.7/dist-packages/django/template/response.py, line 105,
in render
[Tue Oct 29 11:17:20 2013] [error] self.content = self.rendered_content
[Tue Oct 29 11:17:20 2013] [error] File
/usr/lib/python2.7/dist-packages/django/template/response.py, line 82, in
rendered_content
[Tue Oct 29 11:17:20 2013] [error] content = template.render(context)
[Tue Oct 29 11:17:20 2013] [error] File
/usr/lib/python2.7/dist-packages/django/template/base.py, line 140, in
render
[Tue Oct 29 11:17:20 2013] [error] return self._render(context)
[Tue Oct 29 11:17:20 2013] [error] File
/usr/lib/python2.7/dist-packages/django/template/base.py, line 134, in
_render
[Tue Oct 29 11:17:20 2013] [error] return self.nodelist.render(context)
[Tue Oct 29 11:17:20 2013] [error] File
/usr/lib/python2.7/dist-packages/django/template/base.py, line 830, in
render
[Tue Oct 29 11:17:20 2013] [error] bit = self.render_node(node,
context)
[Tue Oct 29 11:17:20 2013] [error] File
/usr/lib/python2.7/dist-packages/django/template/base.py, line 844, in
render_node
[Tue Oct 29 11:17:20 2013] [error] return node.render(context)
[Tue Oct 29 11:17:20 2013] [error] File
/usr/lib/python2.7/dist-packages/django/template/defaulttags.py, line
Re: [Openstack] Is there any way to extend the ip address of subnet?
From my experience, it is rather safe to extend allocation pools directly in the database. We also did allocation pool shrinking but always make sure there is no IP associated (or even assigned to a project) from out of the new range. Check the neutron MySQL table: ipallocationpools. Regards, Daniel - Original Message - From: Aaron Rosen aro...@nicira.com To: Sam Lee lixq2...@gmail.com Cc: openstack openstack@lists.openstack.org Sent: Thursday, November 7, 2013 4:28:44 AM Subject: Re: [Openstack] Is there any way to extend the ip address of subnet? Hi Sam, Unfortunately we do not support updating the allocation-pools on subnets at this time. This is something that we should definitely fix though in neutron. Aaron On Wed, Nov 6, 2013 at 10:46 PM, Sam Lee lixq2...@gmail.com wrote: Hi All, I have created a subnet with 10 ips. But now I need more than ten instances, is there any way to extend the subnet to add ip address? eg: I have ten ips as following: 172.16.2.210 ~ 172.16.2.220 I want to add 20 more ips, and so the result will be 172.16.2.210 ~ 172.16.2.230 I try subnet-update command and create a new subnet with the same CIDR, but it doesn't work correctly. Thanks in advance. ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Re: [Openstack] How to copy vol to image?
You can check into the glance logs to see if its receives the API calls at first, and eventually if you see any errors. That happens sometimes Regards, Razique On 6 Nov 2013 at 19:42:20, Li, Leon (leon@emc.com) wrote: Hi, Anyone knows how to create image from vol? First I have created a volume based on an image. After I did “cinder upload-to-image volumeID image2”, the volume will become “uploading” status for a while. After several minutes, vol status will be “available” again. However, I can’t find out where is the new image. Both “glance image-list” and “cinder list” can’t show the new image. Leon ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Re: [Openstack] Is there a way to tell Nova not to count NFS-mounted instances directory to disk space on each node?
Hey Daniel, Doesn’t seem possible at the moment looks like... -- Razique On 7 Nov 2013 at 02:09:15, Daniel Speichert (dan...@speichert.pl) wrote: Hi All, We have a couple of compute nodes each having its /var/lib/nova/instances directory mounted via NFS from shared storage server. Nova gathers free space statistics from each compute node and adds them, making the theoretical total disk space equal N times the real one (N is the number of nodes we have). Is there a way to tell it not to count this space again on some nodes? Regards, Daniel Speichert ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
[Openstack] Dashboard Overview tab shows 2 phantom instances
Hi list, The Overview tab from dashboard shows on used metric 2 extra instances: - if i have no instances created in the Instances tab it will show Instances Used 2 of 30 - if there are n instances created it will show Instances Used n+2 of 30 In the nova db i have the correct number of instances: - SELECT * FROM nova.instances where vm_state'deleted'; returns 0 This may have happened when I got a kernel crash. I would like to know from what table is reading the information, in order to manually correct it? Thank you, Cristian Falcas ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Re: [Openstack] No IP assigned to VM by DHCP
l3 agent does not required for dhcp agent to provide addresses. They
are, actually, seraprate OVS bridges on network node.
On 07.11.2013 19:01, Molnár Mihály László wrote:
Hi!
Do you have l3 agent configured? I dont know havana, but should look
like this:
*
Create a router for the new tenant:
quantum router-create --tenant-id $put_id_of_project_one router_proj_one
*
Add the router to the running l3 agent (if it wasn't automatically
added):
quantum agent-list (to get the l3 agent ID)
quantum l3-agent-router-add $l3_agent_ID router_proj_one
From Grizzly install guide:
https://github.com/mseknibilel/OpenStack-Grizzly-Install-Guide/blob/OVS_MultiNode/OpenStack_Grizzly_Install_Guide.rst
Rusty
On Thu, Nov 7, 2013 at 5:45 PM, Therese Persson
therese.pers...@ericsson.com mailto:therese.pers...@ericsson.com
wrote:
Hi,
I have a multi-node installation of OpenStack Havana, one
controller node, one network node and at the moment only one
compute node.
When creating a VM no IP is assigned by DHCP. It seems to be a
problem with the openvswitch plugin on the controller node, it
fails to start.
I also get a lot of error messages in my logs (controller node):
/var/log/neutron/openvswitch-agent.log
2013-11-07 16:03:59.453 4317 ERROR
neutron.plugins.openvswitch.agent.ovs_neutron_agent [-] Tunneling
cannot be enabled without a valid local_ip. Agent terminated!
/var/log/neutron/server.log
2013-11-07 16:03:55.584 4230 ERROR neutron.common.legacy [-]
Skipping unknown group key: firewall_driver
2013-11-07 16:03:55.907 4230 WARNING neutron.api.extensions [-]
Extension fwaas not supported by any of loaded plugins
2013-11-07 16:03:55.908 4230 WARNING neutron.api.extensions [-]
Extension lbaas not supported by any of loaded plugins
2013-11-07 16:03:55.911 4230 WARNING neutron.api.extensions [-]
Extension port-security not supported by any of loaded plugins
2013-11-07 16:03:55.912 4230 WARNING neutron.api.extensions [-]
Extension router-service-type not supported by any of loaded plugins
2013-11-07 16:03:55.914 4230 WARNING neutron.api.extensions [-]
Extension routed-service-insertion not supported by any of loaded
plugins
2013-11-07 16:03:55.915 4230 WARNING neutron.api.extensions [-]
Extension vpnaas not supported by any of loaded plugins
2013-11-07 16:03:55.916 4230 WARNING neutron.api.extensions [-]
Extension lbaas_agent_scheduler not supported by any of loaded plugins
2013-11-07 16:03:55.918 4230 WARNING neutron.api.extensions [-]
Extension multi-provider not supported by any of loaded plugins
2013-11-07 16:03:55.919 4230 WARNING neutron.api.extensions [-]
Extension service-type not supported by any of loaded plugins
2013-11-07 16:03:55.919 4230 WARNING neutron.api.extensions [-]
Extension flavor not supported by any of loaded plugins
2013-11-07 16:03:55.920 4230 WARNING neutron.api.extensions [-]
Extension metering not supported by any of loaded plugins
2013-11-07 16:03:55.943 4230 WARNING
keystoneclient.middleware.auth_token [-] Configuring auth_uri to
point to the public identity endpoint is required; clients may not
be able to authenticate against an admin endpoint
2013-11-07 16:12:56.433 4230 WARNING neutron.db.agentschedulers_db
[-] Fail scheduling network {'status': u'ACTIVE', 'subnets':
[u'1190fcaf-211a-59a9-b0fd-4cca9441ce1f'], 'name': u'net1',
'provider:physical_network': None, 'admin_state_up': True,
'tenant_id': u'519c6e2d263044adba404441f18aab60',
'provider:network_type': u'gre', 'router:external': False,
'shared': False, 'id': u'b2565410-baa1-458a-82a0-a930d3891bbd',
'provider:segmentation_id': 1L}
/var/log/keystone/keystone.conf
2013-11-07 14:46:36.146 1409 WARNING keystone.common.wsgi [-]
Authorization failed. The request you have made requires
authentication. from 127.0.0.1
Configuration files:
/etc/neutron/api-paste.ini
[composite:neutron]
use = egg:Paste#urlmap
/: neutronversions
/v2.0: neutronapi_v2_0
[composite:neutronapi_v2_0]
use = call:neutron.auth:pipeline_factory
noauth = extensions neutronapiapp_v2_0
keystone = authtoken keystonecontext extensions neutronapiapp_v2_0
[filter:keystonecontext]
paste.filter_factory = neutron.auth:NeutronKeystoneContext.factory
[filter:authtoken]
paste.filter_factory =
keystoneclient.middleware.auth_token:filter_factory
auth_host = 10.10.10.51 tel:10.10.10.51
#auth_uri=http://10.10.10.51 tel:10.10.10.51:5000
auth_port = 35357
auth_protocol = http
admin_tenant_name = service
admin_user = neutron
admin_password = neutron
[filter:extensions]
paste.filter_factory =
neutron.api.extensions:plugin_aware_extension_middleware_factory
[app:neutronversions]
paste.app_factory =
Re: [Openstack] Is there a way to tell Nova not to count NFS-mounted instances directory to disk space on each node?
I think it would make sense to have an entry in the nova.conf file on a compute node to indicate that the instances are mounted on shared storage. This could be fed back into the database, used in resource reporting (like in this case where it affects the real amount of storage available), and could also be added to the instance itself so that the evacuate/migrate commands could programmatically determine whether the instance is on shared storage or not instead of requiring the user to specify it. Chris On 11/07/2013 04:36 AM, Razique Mahroua wrote: Hey Daniel, Doesn’t seem possible at the moment looks like... -- Razique On 7 Nov 2013 at 02:09:15, Daniel Speichert (dan...@speichert.pl mailto://dan...@speichert.pl) wrote: Hi All, We have a couple of compute nodes each having its /var/lib/nova/instances directory mounted via NFS from shared storage server. Nova gathers free space statistics from each compute node and adds them, making the theoretical total disk space equal N times the real one (N is the number of nodes we have). Is there a way to tell it not to count this space again on some nodes? Regards, Daniel Speichert ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Re: [Openstack] Is there a way to tell Nova not to count NFS-mounted instances directory to disk space on each node?
I think during the migrations, the compute topic already checks whether or not the storage is a shared one -- Razique On 7 Nov 2013 at 10:11:24, Chris Friesen (chris.frie...@windriver.com) wrote: I think it would make sense to have an entry in the nova.conf file on a compute node to indicate that the instances are mounted on shared storage. This could be fed back into the database, used in resource reporting (like in this case where it affects the real amount of storage available), and could also be added to the instance itself so that the evacuate/migrate commands could programmatically determine whether the instance is on shared storage or not instead of requiring the user to specify it. Chris On 11/07/2013 04:36 AM, Razique Mahroua wrote: Hey Daniel, Doesn’t seem possible at the moment looks like... -- Razique On 7 Nov 2013 at 02:09:15, Daniel Speichert (dan...@speichert.pl mailto://dan...@speichert.pl) wrote: Hi All, We have a couple of compute nodes each having its /var/lib/nova/instances directory mounted via NFS from shared storage server. Nova gathers free space statistics from each compute node and adds them, making the theoretical total disk space equal N times the real one (N is the number of nodes we have). Is there a way to tell it not to count this space again on some nodes? Regards, Daniel Speichert ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
[Openstack] Cleaning after tests
Hello,
I'm trying to use tempest tests to testing openstack installation. I'm using
branch stable/grizzly and I can't now upgrade it to havana. My problem is that
if some test has got error e.g. test instance is not created propery than in
openstack database remains a lot of unecessary instances, tenants, user and
other data.
I try to fix some tests to catch errors in few places and clean after such
errors but there are place that I have no idea how to clean. E.g. in test:
test_server_security_groups(self)
from tempest/tests/compute/security_groups/test_security_groups.py
if in code:
# Create server and add the security group created
# above to the server we just created
server_name = rand_name('server')
resp, server = self.servers_client.create_server(server_name,
self.image_ref,
self.flavor_ref)
server_id = server['id']
self.servers_client.wait_for_server_status(server_id, 'ACTIVE')
is not created properly than this instance is in database with state ERROR
and it is not deleted. Also tenant and user which was earlier created in test
class are not deleted.
So maybe someone of You have got such problem and know how to clean database
after tempest tests?
---
Regards,
Sławek Kapłoński
sla...@kaplonski.pl
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Re: [Openstack] Is there a way to tell Nova not to count NFS-mounted instances directory to disk space on each node?
Thank you both for your answers. What Chris describes is definitely a good approach. I think it's worth filing a wish bug. I can do it unless you want to describe your idea, Chris. Regards, Daniel - Original Message - From: Chris Friesen chris.frie...@windriver.com To: openstack@lists.openstack.org Sent: Thursday, November 7, 2013 12:57:25 PM Subject: Re: [Openstack] Is there a way to tell Nova not to count NFS-mounted instances directory to disk space on each node? I think it would make sense to have an entry in the nova.conf file on a compute node to indicate that the instances are mounted on shared storage. This could be fed back into the database, used in resource reporting (like in this case where it affects the real amount of storage available), and could also be added to the instance itself so that the evacuate/migrate commands could programmatically determine whether the instance is on shared storage or not instead of requiring the user to specify it. Chris On 11/07/2013 04:36 AM, Razique Mahroua wrote: Hey Daniel, Doesn’t seem possible at the moment looks like... -- Razique On 7 Nov 2013 at 02:09:15, Daniel Speichert (dan...@speichert.pl mailto://dan...@speichert.pl) wrote: Hi All, We have a couple of compute nodes each having its /var/lib/nova/instances directory mounted via NFS from shared storage server. Nova gathers free space statistics from each compute node and adds them, making the theoretical total disk space equal N times the real one (N is the number of nodes we have). Is there a way to tell it not to count this space again on some nodes? Regards, Daniel Speichert ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Re: [Openstack] Is there a way to tell Nova not to count NFS-mounted instances directory to disk space on each node?
On 11/07/2013 12:52 PM, Daniel Speichert wrote: Thank you both for your answers. What Chris describes is definitely a good approach. I think it's worth filing a wish bug. I can do it unless you want to describe your idea, Chris. If you want to run with it, go for it. :) I'd appreciate it if you could let me know if it goes anywhere... I think it's probably also worth filing a bug for multiple-counting of shared instance storage. Chris ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Re: [Openstack] Is there a way to tell Nova not to count NFS-mounted instances directory to disk space on each node?
I definitely agree with you Chris -- Razique On 7 Nov 2013 at 11:08:33, Chris Friesen (chris.frie...@windriver.com) wrote: On 11/07/2013 12:53 PM, Razique Mahroua wrote: I think during the migrations, the compute topic already checks whether or not the storage is a shared one You are correct, but it does it by creating a temporary file on one node and testing for it on the other node. Kind of ugly, and this technique doesn't work for the evacuate case where one of the compute nodes is down. Also, the nova host-evacuate command currently cannot handle a mix of instances on local storage and instances booting from cinder volumes (which counts as shared storage, as far as I can tell). So you have to do all of one type one at a time, and then you can do the rest all in a bunch. Chris ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Re: [Openstack] Is there a way to tell Nova not to count NFS-mounted instances directory to disk space on each node?
There is compute_nodes file in /var/lib/nova/instances with the hostnames of all compute nodes using that storage so it should be possible and easy to figure out if that is a shared storage or not. Regards, Daniel - Original Message - From: Razique Mahroua razique.mahr...@gmail.com To: Chris Friesen chris.frie...@windriver.com, openstack@lists.openstack.org Sent: Thursday, November 7, 2013 1:53:29 PM Subject: Re: [Openstack] Is there a way to tell Nova not to count NFS-mounted instances directory to disk space on each node? I think during the migrations, the compute topic already checks whether or not the storage is a shared one -- Razique On 7 Nov 2013 at 10:11:24, Chris Friesen ( chris.frie...@windriver.com ) wrote: I think it would make sense to have an entry in the nova.conf file on a compute node to indicate that the instances are mounted on shared storage. This could be fed back into the database, used in resource reporting (like in this case where it affects the real amount of storage available), and could also be added to the instance itself so that the evacuate/migrate commands could programmatically determine whether the instance is on shared storage or not instead of requiring the user to specify it. Chris On 11/07/2013 04:36 AM, Razique Mahroua wrote: Hey Daniel, Doesn’t seem possible at the moment looks like... -- Razique On 7 Nov 2013 at 02:09:15, Daniel Speichert (dan...@speichert.pl mailto://dan...@speichert.pl) wrote: Hi All, We have a couple of compute nodes each having its /var/lib/nova/instances directory mounted via NFS from shared storage server. Nova gathers free space statistics from each compute node and adds them, making the theoretical total disk space equal N times the real one (N is the number of nodes we have). Is there a way to tell it not to count this space again on some nodes? Regards, Daniel Speichert ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Re: [Openstack] Is there any way to extend the ip address of subnet?
Thank you all of you. I will update db directly for now. @Harshad, I have tried to create a new subnet, but there is something wrong with the CIDR of subnet. for example, Quantum considers CIDR 172.16.0.0/16and 172.16.2.0/24 are the same. I only has ip address 172.16.0.0/16 for floatingip. 2013/11/8 Robert Collins robe...@robertcollins.net I've reopened https://bugs.launchpad.net/neutron/+bug/572 as you say it should be supported :) On 7 November 2013 22:28, Aaron Rosen aro...@nicira.com wrote: Hi Sam, Unfortunately we do not support updating the allocation-pools on subnets at this time. This is something that we should definitely fix though in neutron. Aaron On Wed, Nov 6, 2013 at 10:46 PM, Sam Lee lixq2...@gmail.com wrote: Hi All, I have created a subnet with 10 ips. But now I need more than ten instances, is there any way to extend the subnet to add ip address? eg: I have ten ips as following: 172.16.2.210 ~ 172.16.2.220 I want to add 20 more ips, and so the result will be 172.16.2.210 ~ 172.16.2.230 I try subnet-update command and create a new subnet with the same CIDR, but it doesn't work correctly. Thanks in advance. ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack -- Robert Collins rbtcoll...@hp.com Distinguished Technologist HP Converged Cloud ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
[Openstack] Meetup in UAE.
Hello Folks, I am planning to have the first meetup of OpenStack User Group in U.A.E, preferably in Dubai. If you are interested in attending the meetup and you are the summit. Please contact me off the list. Thanks. Best regards, Syed Armani ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Re: [Openstack] Unauthorized error
Hi Pax Hope your problem is resolved. What was the final issue ? -Dheerendra On Thu, Nov 7, 2013 at 12:19 PM, Dheerendra dheerendra.madhusudh...@gmail.com wrote: Hi Pax 1. Did you create user, tenant and role ? 2. Did you add the user and role ? 3. Did you define the service-list and endpoint ? 4. Can you run the command 'keystone user-list', 'keystone tenant-list', 'keystone role-list', 'keystone endpoint-list' and keystone service-list' ? 5. You can send us the keystone.conf and keystone logs. I can check that. 6. Look at the /var/log/apache2/error.log. All this may give you good inputs for you to troubleshoot. If you need any help do let me know. Please ensure that everything is working fine as given in the following link. If not do let me know which step is failing. http://docs.openstack.org/havana/install-guide/install/apt/content/ch_keystone.html -Dheerendra On Wed, Nov 6, 2013 at 5:28 PM, Pax Mridhul mrid...@live.com wrote: Hello, I just finished installing openstack on my server and I'm getting a bunch of unauthorized errors when I load my dashborad home page. Error screenshot attatched. Is there anything I did wrong while configuring keystone ? Appreciate your help. ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
