{ "info": { "author": "Alvaro Lopez Garcia", "author_email": "aloga@ifca.unican.es", "bugtrack_url": null, "classifiers": [ "Intended Audience :: Information Technology", "Intended Audience :: System Administrators", "License :: OSI Approved :: Apache Software License", "Operating System :: POSIX :: Linux", "Programming Language :: Python", "Programming Language :: Python :: 2", "Programming Language :: Python :: 2.6", "Programming Language :: Python :: 2.7", "Topic :: System :: Monitoring" ], "description": "# Cloud BDII provider\n\nThe Cloud BDII provider generates a GlueSchema v2 representation of cloud\nresources for publihing it into a BDII\n\n## Installation\n\n### Binary packages\n\nPackages are available at [EGI's AppDB](https://appdb.egi.eu/store/software/cloud.info.provider).\nUse the appropriate repos for your distribution and install using the usual tools.\n\n### From source\n\nGet the source by cloning this repo and do a pip install:\n\n```\ngit clone https://github.com/EGI-FCTF/BDIIscripts\ncd BDIIscripts \npip install .\n```\n\nIf you plan to use the script in a bdii, the `bdii` package should be also installed\n(it should be available in standard OS repositories).\n\n## Generation of the LDIF\u00a0\n\nThe cloud-info-provider generates a LDIF according to the information in a\nyaml file describing the static information of the cloud resources.\nBy default `/etc/cloud-info-provider/bdii.yaml` is used, but this path can be\noverriden with the `--yaml-file` option. A complete example with comments is\navailable in the `sample.static.yaml` file.\n\nDynamic information can be further obtained with the middleware providers\n(OpenStack and OpenNebula via rOCCI supported currently). Use the\n`--middleware` option for specifying the provider to use (see the command\nhelp for exact names). cloud-info-provider will fallback to static information\ndefined in the yaml file if a dynamic provider is not able to return any\ninformation. See the `sample.openstack.yaml` and `sample.opennebularocci.yaml`\nfor example configurations for each provider.\n\nThere are three different maps in the yaml file considered by the provider:\n`site`, `compute`, and `storage`:\n * `site` contains basic information of the site. The only attribute to define\n here is the `name` which must contain the site name as defined in GOCDB.\n Alternatively, the site name can be fetched from\n `/etc/glite-info-static/site/site.cfg` (or by the file set with the\n `--glite-site-info-static` option).\n Any other information is only relevant to generate a LDIF for a complete \n site-BDII (*this is not the recommended deployment mode*).\n \n * `compute` should be present for those sites providing a IaaS computing\n service. It describes the available resources, service endpoints,\n the available VM images and the templates to run those images.\n Dynamic providers will fetch most of the information in this section.\n See the sample yaml files for details.\n\n * `storage` should be present for sites providing IaaS storage service.\n Similarly to the `compute`, it contains a description of the resources\n and enpoints providing the service. There are no dynamic providers for\n `storage`at the moment.\n\nEach dynamic provider has its own commandline options for specifying how\nto connect to the underlying service. Use the `--help` option for a complete\nlisting of options.\n\nFor example for OpenStack, use a command line similar to the following:\n```\ncloud-info-provider-service --yaml-file /etc/cloud-info-provider/bdii.yaml \\\n --middleware OpenStack --os-username --os-password \\\n --os-tenant-name --os-auth-url \n```\n\n**Test the generation of the LDIF before running the provider into your BDII!**\n\n## Running the provider in a resource-BDII\n\nThis is the normal deployment mode for the cloud provider. It should be installed\nin a node with access to your cloud infrastructure: for OpenStack, access to\nnova service is needed; for OpenNebula-rOCCI provider, access to the files\ndescribing the rOCCI templates is needed (e.g. installing the provider in the same\nhost as rOCCI-server).\n\n### Create the provider script\n\nIn `/var/lib/bdii/gip/provider/` create a `cloud-info-provider` file that \ncalls the provider with the correct options for your site:\n\n```\n#!/bin/sh\n\ncloud-info-provider-service --yaml /etc/cloud-info-provider/openstack.yaml \\\n --middleware openstack \\\n --os-username --os-password \\\n --os-tenant-name --os-auth-url \n\n```\n\nGive execution permission:\n```\nchmod +x /var/lib/bdii/gip/provider/cloud-info-provider\n```\nand test it:\n```\n/var/lib/bdii/gip/provider/cloud-info-provider\n```\nIt should output the full ldif describing your site.\n\n### Start the bdii service\n\nOnce the provider script is working, start the bdii service:\n```\nservice bdii start\n```\n\nThe ldap server should contain all your cloud resource information:\n```\nldapsearch -x -h localhost -p 2170 -b o=glue\n```\n\n##\u00a0Adding the resource provider in a site-BDII\n\nSites should have a dedicated host for the site-BDII. Information on how to\nset up this machine is avaiable in the EGI.eu wiki at\n[How to publish site information](https://wiki.egi.eu/wiki/MAN01_How_to_publish_Site_Information). \n\nAdd your cloud-info-provider to your site-BDII by adding a new URL like this:\n```\nldap://:2170/GLUE2GroupID=cloud,o=glue\n```\n\n## Running the cloud-provider as a full site-BDII\n\n**This is not recommended for production!!**\n\nIf your site does not have a site-BDII and you want to generate both the\nresource information and the site information with the cloud-bdii-provider\nyou can add in the `/var/lib/bdii/gip/provider/cloud-info-provider` the\n`--full-bdii-info` option to the `cloud-info-provider-service`. The YAML\nfile must contain all your site information as described in the templates.", "description_content_type": null, "docs_url": null, "download_url": "UNKNOWN", "downloads": { "last_day": -1, "last_month": -1, "last_week": -1 }, "home_page": "UNKNOWN", "keywords": null, "license": "UNKNOWN", "maintainer": null, "maintainer_email": null, "name": "cloud-bdii-provider", "package_url": "https://pypi.org/project/cloud-bdii-provider/", "platform": "UNKNOWN", "project_url": "https://pypi.org/project/cloud-bdii-provider/", "project_urls": { "Download": "UNKNOWN", "Homepage": "UNKNOWN" }, "release_url": "https://pypi.org/project/cloud-bdii-provider/0.4.dev140.g387348d/", "requires_dist": null, "requires_python": null, "summary": "Cloud BDII info provider", "version": "0.4.dev140.g387348d" }, "last_serial": 1249253, "releases": { "0.4.dev140.g387348d": [ { "comment_text": "", "digests": { "md5": "248089eb0599ca666bd38f231828b378", "sha256": "bf1d497f5a2cc63b668b43d08fe7b71584cddf3c16ba4452239aec25b96280f3" }, "downloads": -1, "filename": "cloud-bdii-provider-0.4.dev140.g387348d.tar.gz", "has_sig": false, "md5_digest": "248089eb0599ca666bd38f231828b378", "packagetype": "sdist", "python_version": "source", "requires_python": null, "size": 32067, "upload_time": "2014-10-06T10:49:31", "url": "https://files.pythonhosted.org/packages/75/88/dec246821c236a503b588769e8531012820b4e27dc21c6c7e402517de86c/cloud-bdii-provider-0.4.dev140.g387348d.tar.gz" } ] }, "urls": [ { "comment_text": "", "digests": { "md5": "248089eb0599ca666bd38f231828b378", "sha256": "bf1d497f5a2cc63b668b43d08fe7b71584cddf3c16ba4452239aec25b96280f3" }, "downloads": -1, "filename": "cloud-bdii-provider-0.4.dev140.g387348d.tar.gz", "has_sig": false, "md5_digest": "248089eb0599ca666bd38f231828b378", "packagetype": "sdist", "python_version": "source", "requires_python": null, "size": 32067, "upload_time": "2014-10-06T10:49:31", "url": "https://files.pythonhosted.org/packages/75/88/dec246821c236a503b588769e8531012820b4e27dc21c6c7e402517de86c/cloud-bdii-provider-0.4.dev140.g387348d.tar.gz" } ] }