[openstack-dev] [nova] How can I continue to complete a abandoned blueprint?
hi all: Bp flavor-quota-memory(https://blueprints.launchpad.net/nova/+spec/flavor-quota-memory) was submitted by my partner in havana. but it has abandoned because of some reason. I want to continue to this blueprint. Based on the rules about BP for kilo, for this bp, spec is not necessary, so I submit the code directly and give commit message to clear out questions in spec. Is it right? how can I do? thanks! -- Name : Li zheming Company : Hua Wei Address ： Shenzhen China Tel：0086 18665391827___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [nova] How can I continue to complete a abandoned blueprint?
thanks! I have submitted a new blueprint(quota-instance-memory) the link is: https://blueprints.launchpad.net/nova/+spec/quota-instance-memory Merry Christmas!^_^ -- Name : Li zheming Company : Hua Wei Address ： Shenzhen China Tel：0086 18665391827 At 2014-12-22 22:32:52,Jay Pipes jaypi...@gmail.com wrote: On 12/22/2014 04:54 AM, li-zheming wrote: hi all: Bp flavor-quota-memory(https://blueprints.launchpad.net/nova/+spec/flavor-quota-memory) was submitted by my partner in havana. but it has abandoned because of some reason. Some reason == the submitter failed to provide any details on how the work would be implemented, what the use cases were, and any alternatives that might be possible. I want to continue to this blueprint. Based on the rules about BP for https://blueprints.launchpad.net/openstack/?searchtext=for kilo, for this bp, spec is not necessary, so I submit the code directly and give commit message to clear out questions in spec. Is it right? how can I do? thanks! Specs are no longer necessary for smallish features, no. A blueprint is still necessary on Launchpad, so you should be able to use the abandoned one you link above -- which, AFAICT, has enough implementation details about the proposed changes. Alternately, if you cannot get the original submitter to remove the spec link to the old spec review, you can always start a new blueprint and we can mark that one as obselete. I'd like Dan Berrange (cc'd) to review whichever blueprint on Launchpad you end up using. Please let us know what you do. 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] [qa] Python 3.3 patches (using six)
+1 2014-03-11 5:54 GMT+08:00 David Kranz dkr...@redhat.com: There are a number of patches up for review that make various changes to use six apis instead of Python 2 constructs. While I understand the desire to get a head start on getting Tempest to run in Python 3, I'm not sure it makes sense to do this work piecemeal until we are near ready to introduce a py3 gate job. Many contributors will not be aware of what all the differences are and py2-isms will creep back in resulting in more overall time spent making these changes and reviewing. Also, the core review team is busy trying to do stuff important to the icehouse release which is barely more than 5 weeks away. IMO we should hold off on various kinds of cleanup patches for now. -David ___ 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] [nova][ec2-api]cmd euca-describle-address will return error. someone can help me?
hi all:
I used euca2tool3.1.10 to test ec2 api.but when I do cmd
euca-describle-address, it return error, like this:
error(notImplementedError):unknown error occured
my environment:
two float IPs:
200.200.130.3- bingding a instance
200.200.130.4-no bingding
if I do cmd euca-describle-addres 200.200.130.4, it return OK.
if I do cmd euca-describle-addres 200.200.130.4, it return:
error(notImplementedError):unknown error occured
if I do cmd euca-describle-addres, it return:
error(notImplementedError):unknown error occured
so I think it is error with floatIP which is bingding in a instance.
I find the code about this:
nova/api/ec2/cloud.py
def _format_address(self, context, floating_ip):
ec2_id = None
if floating_ip['fixed_ip_id']:
fixed_id = floating_ip['fixed_ip_id']
fixed = self.network_api.get_fixed_ip(context, fixed_id)
if fixed['instance_uuid'] is not None:
ec2_id = ec2utils.id_to_ec2_inst_id(fixed['instance_uuid'])
address = {'public_ip': floating_ip['address'],
'instance_id': ec2_id}
if context.is_admin:
details = %s (%s) % (address['instance_id'],
floating_ip['project_id'])
address['instance_id'] = details
return address
if floatIP which bingding instance, it will enter in the red code. it
will
enter function .get_fixed_ip(context, fixed_id), but in get_finxd_ip:
nova/network/neutronv2/api.py:
def get_fixed_ip(self, context, id):
Get a fixed ip from the id.
raise NotImplementedError()
it raise exception NotImplementedError.
so I have two questions:
1. the method of the test is OK?whether I do cmd error?
2. whether the neutron client unsupport get_fixed_ip by id?
thanks!
lizheming
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [nova]can someone help me? when I use cmd nova migration-list error.
Ok .thanks Jay
I consider it is error in novaclient before.
it is my misunderstand. thank you very much!
lizheming
2014/1/20 Jay Lau jay.lau@gmail.com
It is being fixed https://review.openstack.org/#/c/61717/
Thanks,
Jay
2014/1/20 li zheming lizhemin...@gmail.com
hi all:
when I use cmd nova migration-list, it return error,like this:
openstack@ openstack@devstack:/home$devstack:/home$ nova
migration-list
ERROR: 'unicode' object has no attribute 'iteritems'
I step the codes and find the codes have some error.
python-novaclient/novaclient/base.py
class Manager(utils.HookableMixin):
..
def _list(self, url, response_key, obj_class=None, body=None):
if body:
_resp, body = self.api.client.post(url, body=body)
else:
_resp, body = self.api.client.get(url)
if obj_class is None:
obj_class = self.resource_class
data = body[response_key]
# NOTE(ja): keystone returns values as list as {'values': [ ... ]}
# unlike other services which just return the list...
if isinstance(data, dict):
try:
data = data['values']
except KeyError:
pass
with self.completion_cache('human_id', obj_class, mode=w):
with self.completion_cache('uuid', obj_class, mode=w):
return [obj_class(self, res, loaded=True)
for res in data if res]
I set a breakpoint in data = data['values'], and find the date
is
{u'objects': []}}, it has no key named values.
it except a keyError and pass.
if go for res in data if res , the res is unicode object,
this will
occur error in the next fun.
do you met this issue? and someone who know why the comment say
keystone
returns values as list as {'values': [ ... ]}
but I think this is not relevant about keystone. may be I
misunderstand this codes. please give me more info about this code.
thank you very much!
___
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] [openstack][keystone] Is the user password too simple?
在2013年12月31 03时15分，Brant Knudsonb...@acm.org写道： On Mon, Dec 30, 2013 at 12:55 AM, li-zheming li-zhem...@163.com wrote: hi all: when create user, you can set user password. You can set password as a simple word 'a'. the password is too simple but not limit. if someone want to steal your password, it is so easily(such as exhaustion). I consider that it must be limited when set password, like this: 1. inlcude uppper and lower letters 2. include nums 3. include particular symbol，such as '_','' 4. the length8 administor can set the password rule. I want to provide a BP about this issue. can you give me some advice or ideas?? thanks! lizheming I'd prefer it if we didn't reinvent this wheel ourselves. If customers need to enforce password strength, expiration, history, user lockout, etc, then they should store users in an LDAP directory that supports these things and configure Keystone to use that. - Brant hi brant: I am sorry, I may be not understand how store users in an LDAP directory that supports these things and configure Keystone to use that. Is there some configure in keystone? ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [openstack][keystone] Is the user password too simple?
hi Thomas: thank you for your suggestion. I agree with you. cracklib is useful to check password. I only give a example to set password, not force use this rule. I think password scheme should be more discussion. I refer to linux password policy. The Linux password rule is configurable. like this: PASS_MAX_DAYS 9 PASS_MIN_DAYS 0 PASS_MIN_LEN 5 PASS_WARN_AGE 7 this is general rule. if you want to set a strength password, you can use pam_cracklib module. so we can also config password policy. someone who don't need a strength password, they can set general rule in keystone.conf. someone who need strength password, they can load cracklib(or others) and check password, and password rule can be set by administor. this is only my idea, can you give me more suggestion?thanks! --lizheming 在2013年12月30 23时15分，Thomas Goirandz...@debian.org写道： On 12/30/2013 02:55 PM, li-zheming wrote: hi all: when create user, you can set user password. You can set password as a simple word 'a'. the password is too simple but not limit. if someone want to steal your password, it is so easily(such as exhaustion). I consider that it must be limited when set password, like this: 1. inlcude uppper and lower letters 2. include nums 3. include particular symbol，such as '_','' 4. the length8 administor can set the password rule. Hi, If you want to check for password complexity, do it the correct way. I'm used to *always* use a password generator that uses only lower case, and removes chars that can be confused with one another, so that you don't have l and 1, or O and 0 in my passwords. Yet, they are high entropy and long. If you just force me to add upper+lower case and add symbols, then you are just annoying me even with my very good passwords. I want to provide a BP about this issue. can you give me some advice or ideas?? Please use a password entropy function. Something like this: https://pypi.python.org/pypi/cracklib Thomas ___ 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] [openstack][keystone] Is the user password too simple?
hi all: when create user, you can set user password. You can set password as a simple word 'a'. the password is too simple but not limit. if someone want to steal your password, it is so easily(such as exhaustion). I consider that it must be limited when set password, like this: 1. inlcude uppper and lower letters 2. include nums 3. include particular symbol，such as '_','' 4. the length8 administor can set the password rule. I want to provide a BP about this issue. can you give me some advice or ideas?? thanks! lizheming ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
