[openstack-dev] glance community image visibility blue print

2016-01-27 Thread Su Zhang 


Hello everyone,

I created another BP for Newton release regarding glance community image
visibility based on Louis Taylor's original BP. I will continue working on
feature. Before I upload our implementation, it will be wonderful if anyone
in glance community can review and approve the BP. It can be found at
https://review.openstack.org/#/c/271019/


Look forward to receiving your reviews.

Thanks,

Su Zhang
Symantec Corporation

__
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 community image visibility blue print ask for review

2016-01-25 Thread Su Zhang 
Hello everyone,

I created another BP for Newton release regarding glance community image
visibility based on Louis Taylor's original BP. I will continue working on
feature. Before I upload our implementation, it will be wonderful if anyone
in glance community can review and approve the BP. It can be found at
https://review.openstack.org/#/c/271019/


Look forward to receiving your reviews.

Thanks,

-- 
Su Zhang
__
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] [congress] Symantec's security group management policies

2015-10-08 Thread Su Zhang 
Hello,

I've implemented a set of security group management policies and already
put them into our usecase doc.
Let me know if you guys have any comments. My policies is called "Security
Group Management "
You can find the use case doc at:
https://docs.google.com/document/d/1ExDmT06vDZjzOPePYBqojMRfXodvsk0R8nRkX-zrkSw/edit#heading=h.6z1ggtfrzg3n

Thanks,

--
Su Zhang
Senior Software Engineer
Symantec Corporation
__
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] differences between def detail() and def index() in glance/registry/api/v1/images.py

2015-09-09 Thread Su Zhang 
Hello,

I am hitting an error and its trace passes def index ()
in glance/registry/api/v1/images.py.

I assume def index() is called by glance image-list. However, while testing
glance image-list I realized that def detail() is called
under glance/registry/api/v1/images.py instead of def index().

Could someone let me know what's the difference between the two functions?
How can I test out def index() under glance/registry/api/v1/images.py
through CLI or API?

Thanks,

-- 
Su Zhang
__
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] [congress] simulation example in the doc not working

2015-08-25 Thread Su Zhang 
Hello,

In simulation examples at
http://congress.readthedocs.org/en/latest/enforcement.html?highlight=simulation
,
the action_policy is replaced with null. However, null is not
considered as a valid policy as I keep receiving 400 errors.
Could someone let me know the easiest way to get around this error?
How to create a simple action policy just for test purpose as of now?

Thanks,

-- 
Su Zhang
__
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 Unit Test failing due to version conflict

2015-08-11 Thread Su Zhang 
/sandbox.py,
line 110, in dump
return cls.dump(cls, cls(repr(exc)))
  File
/opt/stack/glance/.venv/local/lib/python2.7/site-packages/setuptools/sandbox.py,
line 110, in dump
return cls.dump(cls, cls(repr(exc)))
  File
/opt/stack/glance/.venv/local/lib/python2.7/site-packages/setuptools/sandbox.py,
line 110, in dump
return cls.dump(cls, cls(repr(exc)))
  File
/opt/stack/glance/.venv/local/lib/python2.7/site-packages/setuptools/sandbox.py,
line 110, in dump
return cls.dump(cls, cls(repr(exc)))
  File
/opt/stack/glance/.venv/local/lib/python2.7/site-packages/setuptools/sandbox.py,
line 110, in dump
return cls.dump(cls, cls(repr(exc)))
  File
/opt/stack/glance/.venv/local/lib/python2.7/site-packages/setuptools/sandbox.py,
line 110, in dump
return cls.dump(cls, cls(repr(exc)))
  File
/opt/stack/glance/.venv/local/lib/python2.7/site-packages/setuptools/sandbox.py,
line 110, in dump
return cls.dump(cls, cls(repr(exc)))
MemoryError
Command /opt/stack/glance/.venv/bin/python setup.py develop failed.
running develop
running egg_info
writing requirements to glance.egg-info/requires.txt
writing glance.egg-info/PKG-INFO
writing top-level names to glance.egg-info/top_level.txt
writing dependency_links to glance.egg-info/dependency_links.txt
writing entry points to glance.egg-info/entry_points.txt
writing pbr to glance.egg-info/pbr.json
[pbr] Processing SOURCES.txt
[pbr] In git context, generating filelist from git
reading manifest template 'MANIFEST.in'
writing manifest file 'glance.egg-info/SOURCES.txt'
running build_ext
Creating
/opt/stack/glance/.venv/lib/python2.7/site-packages/glance.egg-link (link
to .)
Adding glance 2015.1.0.0rc2 to easy-install.pth file
Installing glance-scrubber script to /opt/stack/glance/.venv/bin
Installing glance-cache-pruner script to /opt/stack/glance/.venv/bin
Installing glance-cache-cleaner script to /opt/stack/glance/.venv/bin
Installing glance-index script to /opt/stack/glance/.venv/bin
Installing glance-api script to /opt/stack/glance/.venv/bin
Installing glance-search script to /opt/stack/glance/.venv/bin
Installing glance-cache-prefetcher script to /opt/stack/glance/.venv/bin
Installing glance-replicator script to /opt/stack/glance/.venv/bin
Installing glance-cache-manage script to /opt/stack/glance/.venv/bin
Installing glance-manage script to /opt/stack/glance/.venv/bin
Installing glance-control script to /opt/stack/glance/.venv/bin
Installing glance-registry script to /opt/stack/glance/.venv/bin

Installed /opt/stack/glance
Processing dependencies for glance==2015.1.0.0rc2
Searching for fixtures1.3.0,=0.3.14
Reading https://pypi.python.org/simple/fixtures/
Reading https://launchpad.net/python-fixtures
Best match: fixtures 1.2.0
Downloading
https://pypi.python.org/packages/source/f/fixtures/fixtures-1.2.0.tar.gz#md5=9ab03b218bd1f05906b22ed5e78259cd
Processing fixtures-1.2.0.tar.gz
Writing /tmp/easy_install-fuvXte/fixtures-1.2.0/setup.cfg
Running fixtures-1.2.0/setup.py -q bdist_egg --dist-dir
/tmp/easy_install-fuvXte/fixtures-1.2.0/egg-dist-tmp-2brSYg

su@ubuntu:/opt/stack/glance$

Thanks,

-- 
Su Zhang
__
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] Fwd: a question regarding the current status of image community visibility support on glance

2015-03-25 Thread Su Zhang 
Hello everyone

I recently came across one glance related pending blueprint (
https://review.openstack.org/#/c/124050/). It raised our interest as we
also want to implement this community visibility for images through glance.
However, after cherry picking the code change (
https://review.openstack.org/#/c/136374/), I was not able to get the
expected result. Instead, I got the following error:


su@ubuntu:/opt/stack/glance/glance/db/sqlalchemy/migrate_repo/versions$
glance image-update --visibility private
4adda55e-fa6e-4605-aa42-aa5faabc04b8
usage: glance [--version] [-d] [-v] [--get-schema] [--timeout TIMEOUT]
[--no-ssl-compression] [-f] [--os-image-url OS_IMAGE_URL]
[--os-image-api-version OS_IMAGE_API_VERSION]
[--profile HMAC_KEY] [-k] [--os-cert OS_CERT]
[--cert-file OS_CERT] [--os-key OS_KEY] [--key-file OS_KEY]
[--os-cacert ca-certificate-file] [--ca-file OS_CACERT]
[--os-username OS_USERNAME] [--os-user-id OS_USER_ID]
[--os-user-domain-id OS_USER_DOMAIN_ID]
[--os-user-domain-name OS_USER_DOMAIN_NAME]
[--os-project-id OS_PROJECT_ID]
[--os-project-name OS_PROJECT_NAME]
[--os-project-domain-id OS_PROJECT_DOMAIN_ID]
[--os-project-domain-name OS_PROJECT_DOMAIN_NAME]
[--os-password OS_PASSWORD] [--os-tenant-id OS_TENANT_ID]
[--os-tenant-name OS_TENANT_NAME] [--os-auth-url OS_AUTH_URL]
[--os-region-name OS_REGION_NAME]
[--os-auth-token OS_AUTH_TOKEN]
[--os-service-type OS_SERVICE_TYPE]
[--os-endpoint-type OS_ENDPOINT_TYPE]
subcommand ...
glance: error: unrecognized arguments: --visibility
4adda55e-fa6e-4605-aa42-aa5faabc04b8



Could any of you kindly give me some hints regarding how to get the issue
fixed (if it is fixable)? Or anywhere I can change to code to enable the
function mentioned in the blueprint?

Any response will be highly appreciated!

-- 
Su Zhang
__
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] a question regarding the current status of image community visibility support

2015-03-25 Thread Su Zhang 
,
image_properties_1.updated_at AS image_properties_1_updated_at,
image_properties_1.deleted_at AS image_properties_1_deleted_at,
image_properties_1.deleted AS image_properties_1_deleted,
image_properties_1.id AS image_properties_1_id, image_properties_1.image_id
AS image_properties_1_image_id, image_properties_1.name AS
image_properties_1_name, image_properties_1.value AS
image_properties_1_value, image_locations_1.created_at AS
image_locations_1_created_at, image_locations_1.updated_at AS
image_locations_1_updated_at, image_locations_1.deleted_at AS
image_locations_1_deleted_at, image_locations_1.deleted AS
image_locations_1_deleted, image_locations_1.id AS image_locations_1_id,
image_locations_1.image_id AS image_locations_1_image_id,
image_locations_1.value AS image_locations_1_value,
image_locations_1.meta_data AS image_locations_1_meta_data,
image_locations_1.status AS image_locations_1_status \nFROM images LEFT
OUTER JOIN image_properties AS image_properties_1 ON images.id =
image_properties_1.image_id LEFT OUTER JOIN image_locations AS
image_locations_1 ON images.id = image_locations_1.image_id \nWHERE
images.id = %s' ('4adda55e-fa6e-4605-aa42-aa5faabc04b8',)

2015-03-25 22:04:54.163 INFO eventlet.wsgi.server
[req-d197339f-dd73-4ad4-88b4-3194d0e23570 8e50cb1c63294e528502abcbdeed8b50
87ab685d55af4882b9af51e3d286ab0b] 172.16.152.171 - - [25/Mar/2015 22:04:54]
GET /v2/images/4adda55e-fa6e-4605-aa42-aa5faabc04b8 HTTP/1.1 500 139
0.078274



Any response will be highly appreciated,


Su

On Wed, Mar 25, 2015 at 6:02 PM, Ian Cordasco ian.corda...@rackspace.com
wrote:

 That specification wasn’t accepted for Kilo. This discussion should be
 taken to the mailing list anyway (openstack-dev).

 On 3/25/15, 19:32, Su Zhang westlif...@gmail.com wrote:

 
 
 Thanks for your response Fei Long!
 
 
 I switched my environment to glance v2.
 However, I am encountering anther error saying that community is not
 one of the valid visibility values.
 Here is the running script in debug mode:
 
 
 su@ubuntu:/opt/stack/glance/glance$ glance --debug image-update
 --visibility community 4adda55e-fa6e-4605-aa42-aa5faabc04b8
 curl -g -i -X GET -H 'User-Agent: python-glanceclient' -H 'Content-Type:
 application/octet-stream' -H 'Accept-Encoding: gzip, deflate, compress'
 -H 'Accept: */*' -H 'X-Auth-Token:
 {SHA1}6ebf15bd27a056d97e4b66d5e6f1a4f27305b7b3'
 http://172.16.152.171:9292/v2/schemas/image
 
 
 HTTP/1.1 200 OK
 date: Thu, 26 Mar 2015 00:21:17 GMT
 content-length: 3867
 content-type: application/json; charset=UTF-8
 x-openstack-request-id: req-req-44ea8ad6-12e9-4a0b-9d93-2127b9f4b4f8
 
 
 {additionalProperties: {type: string}, name: image, links:
 [{href: {self}, rel: self}, {href: {file}, rel:
 enclosure}, {href: {schema}, rel: describedby}], properties:
 {status: {enum: [queued, saving, active,
  killed, deleted, pending_delete], type: string, description:
 Status of the image (READ-ONLY)}, tags: {items: {type: string,
 maxLength: 255}, type: array, description: List of strings
 related to the image}, kernel_id: {pattern:
 
 ^([0-9a-fA-F]){8}-([0-9a-fA-F]){4}-([0-9a-fA-F]){4}-([0-9a-fA-F]){4}-([0-
 9a-fA-F]){12}$, type: string, description: ID of image stored in
 Glance that should be used as the kernel when booting an AMI-style
 image., is_base: false}, container_format:
  {enum: [null, ami, ari, aki, bare, ovf, ova], type:
 [null, string], description: Format of the container}, min_ram:
 {type: integer, description: Amount of ram (in MB) required to
 boot image.}, ramdisk_id: {pattern:
 ^([0-9a-fA-F]){8}-([0-9a-fA-F]){4}-([0-9a-fA-F]){4}-([0-9a-fA-F]){4}-([0-
 9a-fA-F]){12}$,
  type: string, description: ID of image stored in Glance that
 should be used as the ramdisk when booting an AMI-style image.,
 is_base: false}, locations: {items: {required: [url,
 metadata], type: object, properties: {url: {type:
  string, maxLength: 255}, metadata: {type: object}}}, type:
 array, description: A set of URLs to access the image file kept in
 external store}, visibility: {enum: [public, private], type:
 string, description: Scope of image
  accessibility}, updated_at: {type: string, description: Date
 and time of the last image modification (READ-ONLY)}, owner: {type:
 [null, string], description: Owner of the image, maxLength:
 255}, file: {type: string, description:
  (READ-ONLY)}, min_disk: {type: integer, description: Amount
 of disk space (in GB) required to boot image.}, virtual_size: {type:
 [null, integer], description: Virtual size of image in bytes
 (READ-ONLY)}, id: {pattern:
 ^([0-9a-fA-F]){8}-([0-9a-fA-F]){4}-([0-9a-fA-F]){4}-([0-9a-fA-F]){4}-([0-
 9a-fA-F]){12}$,
  type: string, description: An identifier for the image}, size:
 {type: [null, integer], description: Size of image file in bytes
 (READ-ONLY)}, instance_uuid: {type: string, description: ID of
 instance used to create this image.,
  is_base: false}, os_distro: {type: string, description:
 Common name of operating system distribution as specified in
 
 
 http