Re: [openstack-dev] Juno Multinode installation error
Hi,
A better place to ask this question would be ask.openstack.org .
Cheers,
Ajaya
On Tue, May 5, 2015 at 4:56 PM, Abhishek Talwar abhishek.tal...@tcs.com
wrote:
Hi Folks,
I am trying to setup a multinode OpenStack. When I boot an instance it is
successfully created but it is going in ERROR state. I have checked the
logs in /var/log/nova/nova-scheduler.log and it gives an Operational error
“database is locked”. Moreover when I check the database there are no
tables getting created in the Nova database, while Neutron and others have
there tables.
The logs are following :
2015-05-05 14:35:13.158 18551 TRACE nova.openstack.common.periodic_task
OperationalError: (OperationalError) database is locked u'UPDATE
reservations SET deleted_at=?, deleted=id, updated_at=updated_at WHERE
reservations.deleted = ? AND reservations.expire ?' ('2015-05-05
09:05:13.150105', 0, '2015-05-05 09:05:13.138314')
2015-05-05 14:35:13.158 18551 TRACE nova.openstack.common.periodic_task
2015-05-05 14:37:47.972 18551 INFO oslo.messaging._drivers.impl_rabbit [-]
Connecting to AMQP server on controller:5672
2015-05-05 14:37:47.991 18551 INFO oslo.messaging._drivers.impl_rabbit [-]
Connected to AMQP server on controller:5672
2015-05-05 15:10:59.535 18551 INFO nova.openstack.common.service [-]
Caught SIGTERM, exiting
2015-05-05 15:11:01.506 19260 AUDIT nova.service [-] Starting scheduler
node (version 2014.2.2)
2015-05-05 15:11:03.691 19260 INFO oslo.messaging._drivers.impl_rabbit
[req-7b53c22a-2161-4f9f-9942-c39ad5b35ca0 ] Connecting to AMQP server on
controller:5672
2015-05-05 15:11:03.747 19260 INFO oslo.messaging._drivers.impl_rabbit
[req-7b53c22a-2161-4f9f-9942-c39ad5b35ca0 ] Connected to AMQP server on
controller:5672
2015-05-05 15:21:55.601 19260 INFO nova.openstack.common.service [-]
Caught SIGTERM, exiting
2015-05-05 15:21:56.568 19542 AUDIT nova.service [-] Starting scheduler
node (version 2014.2.2)
2015-05-05 15:21:57.504 19542 INFO oslo.messaging._drivers.impl_rabbit
[req-ee9a2d39-678d-48c2-b490-2894cb6370b5 ] Connecting to AMQP server on
controller:5672
2015-05-05 15:21:57.514 19542 INFO oslo.messaging._drivers.impl_rabbit
[req-ee9a2d39-678d-48c2-b490-2894cb6370b5 ] Connected to AMQP server on
controller:5672
2015-05-05 15:32:39.316 19542 INFO oslo.messaging._drivers.impl_rabbit [-]
Connecting to AMQP server on controller:5672
2015-05-05 15:32:39.343 19542 INFO oslo.messaging._drivers.impl_rabbit [-]
Connected to AMQP server on controller:5672
2015-05-05 15:38:21.280 19542 INFO nova.openstack.common.service [-]
Caught SIGTERM, exiting
2015-05-05 15:38:22.434 19954 AUDIT nova.service [-] Starting scheduler
node (version 2014.2.2)
2015-05-05 15:38:23.173 19954 INFO oslo.messaging._drivers.impl_rabbit
[req-b65ec7c6-6bbd-4e13-9694-da927c9cf337 ] Connecting to AMQP server on
controller:5672
2015-05-05 15:38:23.248 19954 INFO oslo.messaging._drivers.impl_rabbit
[req-b65ec7c6-6bbd-4e13-9694-da927c9cf337 ] Connected to AMQP server on
controller:5672
2015-05-05 15:39:46.468 19954 INFO oslo.messaging._drivers.impl_rabbit [-]
Connecting to AMQP server on controller:5672
2015-05-05 15:39:46.484 19954 INFO oslo.messaging._drivers.impl_rabbit [-]
Connected to AMQP server on controller:5672
The configuration for nova.conf is :
[DEFAULT]
dhcpbridge_flagfile=/etc/nova/nova.conf
dhcpbridge=/usr/bin/nova-dhcpbridge
logdir=/var/log/nova
state_path=/var/lib/nova
lock_path=/var/lock/nova
force_dhcp_release=True
libvirt_use_virtio_for_bridges=True
verbose=True
ec2_private_dns_show_ip=True
api_paste_config=/etc/nova/api-paste.ini
enabled_apis=ec2,osapi_compute,metadata
scheduler_default_filters=AllHostsFilter
verbose = True
connection = mysql://nova:NOVA_DBPASS@controller/nova
rpc_backend = rabbit
rabbit_host = controller
rabbit_password = RABBIT_PASS
auth_strategy = keystone
my_ip = 10.10.10.10
vncserver_listen = 10.10.10.10
vncserver_proxyclient_address = 10.10.10.10
network_api_class = nova.network.neutronv2.api.API
security_group_api = neutron
linuxnet_interface_driver = nova.network.linux_net.LinuxOVSInterfaceDriver
firewall_driver = nova.virt.firewall.NoopFirewallDriver
[keystone_authtoken]
auth_uri = http://controller:5000/v2.0
identity_uri = http://controller:35357
admin_tenant_name = service
admin_user = nova
admin_password = NOVA_PASS
[glance]
host = controller
[neutron]
url = http://controller:9696
auth_strategy = keystone
admin_auth_url = http://controller:35357/v2.0
admin_tenant_name = service
admin_username = neutron
admin_password = NEUTRON_PASS
The configuration for neutron is:
[DEFAULT]
verbose = True
lock_path = $state_path/lock
core_plugin = ml2
service_plugins = router
allow_overlapping_ips = True
auth_strategy = keystone
# Driver to use for scheduling a loadbalancer pool to an lbaas agent
# loadbalancer_pool_scheduler_driver =
neutron.services.loadbalancer.agent_scheduler.ChanceScheduler
Re: [openstack-dev] [Neutron][Keystone] [Nova] How to validate teanant-id for admin operation
On Mon, Apr 27, 2015 at 6:05 AM, Jamie Lennox jamielen...@redhat.com wrote: Not to speak for Brant, but i think the confusion here is why you are doing this. From my perspective you should never be in a position where the admin has to enter a raw project id like that. Sometimes you have to do just that. For e.g. adding a member to an image in glance. Glance does not verify whether the member being added is a valid project_id. I think the problem here is the assumption of an all powerful admin user, and i'd encourage you to change your policy files to scrap that idea. If there is no powerful admin user then how do you deal with situations where a cloud user deletes a project and there are resources(vm, network, block, image) tied to this project across components. Cheers, Ajaya - Original Message - From: German Eichberger german.eichber...@hp.com To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org Sent: Saturday, 25 April, 2015 8:55:23 AM Subject: Re: [openstack-dev] [Neutron][Keystone] [Nova] How to validate teanant-id for admin operation Hi Brant, Sorry, for being confusing earlier. We have operations an administrator/operator is performing on behalf of a user, e.g. “Create Loadbalancer X for user tenant-id 123”. Now we are not checking the tenant-id and are wondering how to make the operation more robust with kesyone’s help. Thanks, German I think the problem here is the assumption of an all powerful admin user, and i'd encourage you to change your policy files to scrap that idea. A role is granted on a project and this project is mentioned in the token. If there is some role that is provided that lets you perform operations outside of the project id specified in that token please file a bug and i'd consider marking it a security issue. The X-Service-Token concept will allow for the combination of a user token and a service token to authenticate an action, so the user can ask for an action to be performed on it's behalf via a service - and in which case the user's project id is communicated via the token. In lieu of all this the quick answer is no. If you are taking a project id from the command line and you want to validate its existence then you have to ask keystone, but you should always be getting this information from a token. Jamie From: Brant Knudson [mailto:b...@acm.org] Sent: Friday, April 24, 2015 11:43 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Neutron][Keystone] [Nova] How to validate teanant-id for admin operation On Fri, Apr 24, 2015 at 11:53 AM, Eichberger, German german.eichber...@hp.com wrote: All, Following up from the last Neutron meeting: If Neutron is performing an operation as an admin on behalf of a user that user's tenant-id (or project-id) isn't validated - in particular an admin can mistype and create object on behalf of non existent users. I am wondering how other projects (e.g. Nova) deal with that and if there is some API support in keystone to save us a round trip (e.g. authenticate admin + validate additional user-id). Not to long ago we got support in the auth_token middleware for a service token in addition to the user's token. The user token is sent in the x-auth-token header and the service token is sent in the x-service-token, and then fields from both tokens are available to the application (e.g., the user project is in HTTP_X_PROJECT_ID and the service token roles are in HTTP_X_SERVICE_ROLES). So you could potentially have a policy rule on the server for the operation that required the service token to have the 'service' role, and what neutron could do is send the original user token in x-auth-token and send its own token as the service token. This seems to be what you're asking for here. - Brant Thanks, German __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development
Re: [openstack-dev] [Neutron][Keystone] [Nova] How to validate teanant-id for admin operation
Hi, You could call GET project/project_id and verify that the project really exists in Keystone. But again by doing that you would be increasing load on Keystone server. When UUID tokens are being used, an additional call is needed to verify the token. If you add another call to this then it would be too much for Keystone server. So none of the other components as of now do this i.e. verify the existence of the project. I don't know if there are any plans to address this. Cheers, Ajaya On Sat, Apr 25, 2015 at 4:25 AM, Eichberger, German german.eichber...@hp.com wrote: Hi Brant, Sorry, for being confusing earlier. We have operations an administrator/operator is performing on behalf of a user, e.g. “Create Loadbalancer X for user tenant-id 123”. Now we are not checking the tenant-id and are wondering how to make the operation more robust with kesyone’s help. Thanks, German *From:* Brant Knudson [mailto:b...@acm.org] *Sent:* Friday, April 24, 2015 11:43 AM *To:* OpenStack Development Mailing List (not for usage questions) *Subject:* Re: [openstack-dev] [Neutron][Keystone] [Nova] How to validate teanant-id for admin operation On Fri, Apr 24, 2015 at 11:53 AM, Eichberger, German german.eichber...@hp.com wrote: All, Following up from the last Neutron meeting: If Neutron is performing an operation as an admin on behalf of a user that user's tenant-id (or project-id) isn't validated - in particular an admin can mistype and create object on behalf of non existent users. I am wondering how other projects (e.g. Nova) deal with that and if there is some API support in keystone to save us a round trip (e.g. authenticate admin + validate additional user-id). Not to long ago we got support in the auth_token middleware for a service token in addition to the user's token. The user token is sent in the x-auth-token header and the service token is sent in the x-service-token, and then fields from both tokens are available to the application (e.g., the user project is in HTTP_X_PROJECT_ID and the service token roles are in HTTP_X_SERVICE_ROLES). So you could potentially have a policy rule on the server for the operation that required the service token to have the 'service' role, and what neutron could do is send the original user token in x-auth-token and send its own token as the service token. This seems to be what you're asking for here. - Brant Thanks, German __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [glance] Why no DB index on sort parameters
Hi All, I see that glance supports arbitrary sort parameters and the default is created_at while listing images. Is there any reason why we don't have index over these fields? If we have an index over these fields then we would avoid a full table scan to do sorting. IMO at least the created_at field should have an index on it. Cheers, Ajaya __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] How to debug test cases in Openstack
Hi, You have a pdb statement somewhere in your test case. Follow this to run a single test with pdb. https://wiki.openstack.org/wiki/Testr Cheers, Ajaya Cheers, Ajaya On Fri, Jan 16, 2015 at 11:07 AM, Abhishek Talwar/HYD/TCS abhishek.tal...@tcs.com wrote: Hi, I have been trying to debug the test cases in OpenStack, but I am not getting successful with it. So if someone can help me with that. The last response from the dev-list was to use $ ./run_tests.sh -d [test module path] but this gives bDb quit error. So kindly help me this. -- Thanks and Regards Abhishek Talwar =-=-= Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [MagnetoDB] TTL feature for a row
Hi guys,
I am referring to the blueprint:
https://blueprints.launchpad.net/magnetodb/+spec/row-expiration . We want
to provide our end users with ttl feature on a row in MagnetoDB.
As it stands today in cassandra, ttl is on a column basis rather than a row
basis. i.e. when you insert a row with an insert statement the ttl is
applied on all the columns. But when you update a row and use ttl there ttl
for only the columns present in SET clause of UPDATE statement.
for e.g if you have a USER table with schema (name text primary key, age
int) and you insert a row with statement INSERT INTO USER(name, age) values
('a', 1) and later update this with UPDATE USER USING TTL 10 set age=2
where name='a', then the age column will get updated and only the age
column will disappear after 10 seconds.
- So in MagnetoDB if a user inserts data without ttl and later updates
the same row with ttl and some updated column values then ttl is only
applied on the updated columns. We should do an insert in this case to make
the whole row disappear. Simlarly if the user inserts the data with a ttl
but updates the data without ttl then we should fetch the ttl for the row
and then update the row with remaining ttl for the row.
- The same problem remains with the conditional update But it's more
difficult to tackle without any locking mechanism.
The simplest solution is to allow ttl only in insert statement and let the
users know about this.
Cheers,
Ajaya
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Keystone] Is anyone working on the following patch?
https://review.openstack.org/#/c/113586/ Two of my patches depend on this patch. https://review.openstack.org/#/c/113277/ https://review.openstack.org/#/c/110575/ Cheers, Ajaya ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [MagnetoDB] Andrey Ostapenko core nomination
+1 Cheers, Ajaya On Fri, Dec 26, 2014 at 8:22 PM, Dmitriy Ukhlov dukh...@mirantis.com wrote: Andrey is very active contributor, good team player and very helps us at previous development cycle. +1 from my side. On Fri, Dec 26, 2014 at 4:16 PM, isviridov isviri...@mirantis.com wrote: Hello stackers and magnetians, I suggest nominating Andrey Ostapenko [1] to MagnetoDB cores. During last months he has made huge contribution to MagnetoDB [2] Andrey drives Tempest and python-magnetodbclient successfully. Please rise your hands. Thank you, Ilya Sviridov [1] http://stackalytics.com/report/users/aostapenko [2] http://stackalytics.com/report/contribution/magnetodb/90 -- Best regards, Dmitriy Ukhlov Mirantis Inc. ___ 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] [glance] Policy file not reloaded after changes
Hi All, The policy file is not reloaded in glance after a change is made to it. You need to restart glance to load the new policy file. I think all other components reload the policy file after a change is made to it. Is it a bug or intended behavior? Cheers, Ajaya ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Quota management and enforcement across projects
Hi, Would the new library support quota on domain level also? As it stands in oslo-incubator it only does quota enforcement on project level only. The use case for this is quota enforcement across multiple projects. For e.g. as a cloud provider, I would like my customer to create only #X volumes across all his projects. -Ajaya Cheers, Ajaya On Wed, Oct 15, 2014 at 7:04 PM, Doug Hellmann d...@doughellmann.com wrote: Sigh. Because I typed the wrong command. Thanks for pointing that out. I don’t see any instances of “quota” in openstack-common.conf files: $ grep quota */openstack-common.conf or in any projects under openstack/“: $ ls */*/openstack/common/quota.py ls: cannot access */*/openstack/common/quota.py: No such file or directory I don’t know where manila’s copy came from, but if it has been copied from the incubator by hand and then changed we should fix that up. Doug On Oct 15, 2014, at 5:28 AM, Valeriy Ponomaryov vponomar...@mirantis.com wrote: But why policy is being discussed on quota thread? On Wed, Oct 15, 2014 at 11:55 AM, Valeriy Ponomaryov vponomar...@mirantis.com wrote: Manila project does use policy common code from incubator. Our small wrapper for it: https://github.com/openstack/manila/blob/8203c51081680a7a9dba30ae02d7c43d6e18a124/manila/policy.py On Wed, Oct 15, 2014 at 2:41 AM, Salvatore Orlando sorla...@nicira.com wrote: Doug, I totally agree with your findings on the policy module. Neutron already has some customizations there and we already have a few contributors working on syncing it back with oslo-incubator during the Kilo release cycle. However, my query was about the quota module. From what I gather it seems not a lot of projects use it: $ find . -name openstack-common.conf | xargs grep quota $ Salvatore On 15 October 2014 00:34, Doug Hellmann d...@doughellmann.com wrote: On Oct 14, 2014, at 12:31 PM, Salvatore Orlando sorla...@nicira.com wrote: Hi Doug, do you know if the existing quota oslo-incubator module has already some active consumers? In the meanwhile I've pushed a spec to neutron-specs for improving quota management there [1] It looks like a lot of projects are syncing the module: $ grep policy */openstack-common.conf barbican/openstack-common.conf:modules=gettextutils,jsonutils,log,local,timeutils,importutils,policy ceilometer/openstack-common.conf:module=policy cinder/openstack-common.conf:module=policy designate/openstack-common.conf:module=policy gantt/openstack-common.conf:module=policy glance/openstack-common.conf:module=policy heat/openstack-common.conf:module=policy horizon/openstack-common.conf:module=policy ironic/openstack-common.conf:module=policy keystone/openstack-common.conf:module=policy manila/openstack-common.conf:module=policy neutron/openstack-common.conf:module=policy nova/openstack-common.conf:module=policy trove/openstack-common.conf:module=policy tuskar/openstack-common.conf:module=policy I’m not sure how many are actively using it, but I wouldn’t expect them to copy it in if they weren’t using it at all. Now, I can either work on the oslo-incubator module and leverage it in Neutron, or develop the quota module in Neutron, and move it to oslo-incubator once we validate it with Neutron. The latter approach seems easier from a workflow perspective - as it avoid the intermediate steps of moving code from oslo-incubator to neutron. On the other hand it will delay adoption in oslo-incubator. The policy module is up for graduation this cycle. It may end up in its own library, to allow us to build a review team for the code more easily than if we put it in with some of the other semi-related modules like the server code. We’re still working that out [1], and if you expect to make a lot of incompatible changes we should delay graduation to make that simpler. Either way, since we have so many consumers, I think it would be easier to have the work happen in Oslo somewhere so we can ensure those changes are useful to and usable by all of the existing consumers. Doug [1] https://etherpad.openstack.org/p/kilo-oslo-library-proposals What's your opinion? Regards, Salvatore [1] https://review.openstack.org/#/c/128318/ On 8 October 2014 18:52, Doug Hellmann d...@doughellmann.com wrote: On Oct 8, 2014, at 7:03 AM, Davanum Srinivas dava...@gmail.com wrote: Salvatore, Joe, We do have this at the moment: https://github.com/openstack/oslo-incubator/blob/master/openstack/common/quota.py — dims If someone wants to drive creating a useful library during kilo, please consider adding the topic to the etherpad we’re using to plan summit sessions and then come participate in the Oslo meeting this Friday 16:00 UTC. https://etherpad.openstack.org/p/kilo-oslo-summit-topics Doug On Wed, Oct 8, 2014 at 2:29 AM, Salvatore Orlando sorla...@nicira.com wrote: On 8 October 2014 04:13, Joe Gordon joe.gord...@gmail.com
Re: [openstack-dev] [MagnetoDB] Core developer nomination
+1 Cheers, Ajaya On Thu, Sep 18, 2014 at 2:38 PM, Dmitriy Ukhlov dukh...@mirantis.com wrote: +1 from me, Charles is very active contributor and I guess if we have such developer in core team MagnetoDB project will become much better that it is now. On Thu, Sep 18, 2014 at 10:09 AM, Illia Khudoshyn ikhudos...@mirantis.com wrote: Congrats, Charles! Great job! On Thu, Sep 18, 2014 at 12:05 AM, Ilya Sviridov isviri...@mirantis.com wrote: Hello magnetodb contributors, I'm glad to nominate Charles Wang to core developers of MagnetoDB. He is top non-core reviewer [1], implemented notifications [2] in mdb and made a great progress with performance, stability and scalability testing of MagnetoDB [1] http://stackalytics.com/report/contribution/magnetodb/90 [2] https://blueprints.launchpad.net/magnetodb/+spec/magnetodb-notifications Welcome to team, Charles! Looking forward for your contribution -- Ilya Sviridov isviridov @ FreeNode -- Best regards, Illia Khudoshyn, Software Engineer, Mirantis, Inc. 38, Lenina ave. Kharkov, Ukraine www.mirantis.com http://www.mirantis.ru/ www.mirantis.ru Skype: gluke_work ikhudos...@mirantis.com ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Best regards, Dmitriy Ukhlov Mirantis Inc. ___ 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] tox -e pep8 fails at requirements.txt
Hi,
It seems like pypi was not reachable at that moment. You could be behind a
proxy. You can try at a later time. It should work.
Cheers,
Ajaya
On Fri, Aug 1, 2014 at 12:29 PM, trinath.soman...@freescale.com
trinath.soman...@freescale.com wrote:
Hi –
When I run tox to check pep8 on the newly cloned neutron from openstack
git , I get the following error.
pep8 create: /root/fw_code_base/neutron_01082014/.tox/pep8
pep8 installdeps: -r/root/fw_code_base/neutron_01082014/requirements.txt,
-r/root/fw_code_base/neutron_01082014/test-requirements.txt
ERROR: invocation failed, logfile:
/root/fw_code_base/neutron_01082014/.tox/pep8/log/pep8-1.log
ERROR: actionid=pep8
msg=getenv
cmdargs=[local('/root/fw_code_base/neutron_01082014/.tox/pep8/bin/pip'),
'install', '-U', '-r/root/fw_code_base/neutron_01082014/requirements.txt',
'-r/root/fw_code_base/neutron_01082014/test-requirements.txt']
env={'PYTHONIOENCODING': 'utf_8', 'XDG_RUNTIME_DIR': '/run/user/0',
'VIRTUAL_ENV': '/root/fw_code_base/neutron_01082014/.tox/pep8', 'LESSOPEN':
'| /usr/bin/lesspipe %s', 'SSH_CLIENT': '10.232.84.77 61736 22', 'LOGNAME':
'root', 'USER': 'root', 'HOME':
'/root/fw_code_base/neutron_01082014/.tox/pep8/tmp/pseudo-home', 'PATH':
'/root/fw_code_base/neutron_01082014/.tox/pep8/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games',
'XDG_SESSION_ID': '19', '_': '/usr/bin/tox', 'SSH_CONNECTION':
'10.232.84.77 61736 10.232.90.26 22', 'LANG': 'en_IN', 'TERM': 'xterm',
'SHELL': '/bin/bash', 'LESSCLOSE': '/usr/bin/lesspipe %s %s', 'LANGUAGE':
'en_IN:en', 'SHLVL': '1', 'SSH_TTY': '/dev/pts/0', 'OLDPWD':
'/root/fw_code_base', 'PWD': '/root/fw_code_base/neutron_01082014',
'PYTHONHASHSEED': '0', 'MAIL': '/var/mail/root', 'LS_COLORS':
'rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arj=01;31:*.taz=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.dz=01;31:*.gz=01;31:*.lz=01;31:*.xz=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.jpg=01;35:*.jpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.axv=01;35:*.anx=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=00;36:*.au=00;36:*.flac=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.axa=00;36:*.oga=00;36:*.spx=00;36:*.xspf=00;36:'}
Downloading/unpacking pbr=0.6,!=0.7,1.0 (from -r
/root/fw_code_base/neutron_01082014/requirements.txt (line 1))
Cannot fetch index base URL https://pypi.python.org/simple/
Could not find any downloads that satisfy the requirement
pbr=0.6,!=0.7,1.0 (from -r
/root/fw_code_base/neutron_01082014/requirements.txt (line 1))
Cleaning up...
No distributions at all found for pbr=0.6,!=0.7,1.0 (from -r
/root/fw_code_base/neutron_01082014/requirements.txt (line 1))
Storing debug log for failure in
/root/fw_code_base/neutron_01082014/.tox/pep8/tmp/pseudo-home/.pip/pip.log
ERROR: could not install deps
[-r/root/fw_code_base/neutron_01082014/requirements.txt,
-r/root/fw_code_base/neutron_01082014/test-requirements.txt]
__ summary
__
ERROR: pep8: could not install deps
[-r/root/fw_code_base/neutron_01082014/requirements.txt,
-r/root/fw_code_base/neutron_01082014/test-requirements.txt]
Can anyone help me on resolving this issue.
Kindly please help me in this regard.
Thanks in advance.
--
Trinath Somanchi - B39208
trinath.soman...@freescale.com | extn: 4048
___
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] Mentor program?
That is a very good suggestion. I started contributing to openstack three months back. IMO it is not that difficult to get started and there are many blogs which can help you get started. There are many low hanging fruits which could be fixed by newbies. The real problem comes when you are post that phase. There are too many projects and it is difficult to select one and work on a small feature from that project. I think we should be concentrating on this part more. The projects which could get most benefit from this are the ones which are not incubated yet or just incubated. Cheers, Ajaya Cheers, Ajaya On Thu, Jul 24, 2014 at 4:12 AM, Joshua Harlow harlo...@outlook.com wrote: Awesome, When I start to see emails on ML that say anyone need any help for XYZ ... (which is great btw) it makes me feel like there should be a more appropriate avenue for those inspirational folks looking to get involved (a ML isn't really the best place for this kind of guidance and directing). And in general mentoring will help all involved if we all do more of it :-) Let me know if any thing is needed that I can possible help with to get more of it going. -Josh On Jul 23, 2014, at 2:44 PM, Jay Bryant jsbry...@electronicjungle.net wrote: Great question Josh! Have been doing a lot of mentoring within IBM for OpenStack and have now been asked to formalize some of that work. Not surprised there is an external need as well. Anne and Stefano. Let me know if the kids anything I can do to help. Jay Hi all, I was reading over a IMHO insightful hacker news thread last night: https://news.ycombinator.com/item?id=8068547 Labeled/titled: 'I made a patch for Mozilla, and you can do it too' It made me wonder what kind of mentoring support are we as a community offering to newbies (a random google search for 'openstack mentoring' shows mentors for GSoC, mentors for interns, outreach for women... but no mention of mentors as a way for everyone to get involved)? Looking at the comments in that hacker news thread, the article itself it seems like mentoring is stressed over and over as the way to get involved. Has there been ongoing efforts to establish such a program (I know there is training work that has been worked on, but that's not exactly the same). Thoughts, comments...? -Josh ___ 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 mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [all] Juno setup
Hi Yogesh, Juno is not released yet. The closest you can get is master. So clone devstack and run ./stack.sh. Thanks, Ajaya Cheers, Ajaya On Fri, Jun 20, 2014 at 12:38 PM, Yogesh Prasad yogesh.pra...@cloudbyte.com wrote: Hi All I want to create a juno setup. Please guide me through any links or processes that needs to be followed to have this setup. *Thanks Regards*, Yogesh Prasad. ___ 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] Recommended way of having a project admin
Hi All, The reason I ask this question in openstack-dev is there is a lot of confusion going around other projects moving to keystone v3. Would it be a problem if I use keystone v3 api for authenticating and point other services to use keystone v2 with keystone v3 token? The main issue here is keystone v2 does not support RBAC policies and other services don't understand keystone v3. Cheers, Ajaya On Wed, May 28, 2014 at 6:28 PM, Ajaya Agrawal ajku@gmail.com wrote: Hi All, We want to introduce a role of project admin in our cloud who can add users only in the project in which he is an admin. AFAIK RBAC policies are not supported by keystone v2 api. So I suppose we will need to use keystone v3 to support the concept of project admin. But I hear things like all the projects don't talk keystone v3 as of now. What is the recommended way of doing it? Cheers, Ajaya ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] Recommended way of having a project admin
Hi All, We want to introduce a role of project admin in our cloud who can add users only in the project in which he is an admin. AFAIK RBAC policies are not supported by keystone v2 api. So I suppose we will need to use keystone v3 to support the concept of project admin. But I hear things like all the projects don't talk keystone v3 as of now. What is the recommended way of doing it? Cheers, Ajaya ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
