Saravanan666/pypi-org huggingface dataset:
Package: openstack-congress
Congress is an open policy framework for the cloud. With Congress, a
cloud operator can declare, monitor, enforce, and audit “policy” in a
heterogeneous cloud environment. Congress gets inputs from a cloud’s
various cloud services; for example in OpenStack, Congress fetches
information about VMs from Nova, and network state from Neutron, etc.
Congress then feeds input data from those services into its policy engine
where Congress verifies that the cloud’s actual state abides by the cloud
operator’s policies. Congress is designed to work withany policyandany cloud service.Free software: Apache licenseDocumentation:https://docs.openstack.org/congress/latest/Wiki:https://wiki.openstack.org/wiki/CongressSource:https://github.com/openstack/CongressBugs:https://bugs.launchpad.net/congressBlueprints:https://blueprints.launchpad.net/congressRelease notes:https://docs.openstack.org/releasenotes/congressAdmin guide:https://docs.openstack.org/congress/latest/admin/index.htmlContributing:https://docs.openstack.org/congress/latest/contributor/index.htmlREST Client：https://opendev.org/openstack/python-congressclientInstalling CongressPlease refer to theinstallation guide
Package: openstack-cyborg
OpenStack Acceleration as a ServiceCyborg provides a general management framework for accelerators such as
FPGA, GPU, SoCs, NVMe SSDs, CCIX caches, DPDK/SPDK, pmem  and so forth.Free software: Apache licenseWiki:https://wiki.openstack.org/wiki/CyborgSource:https://opendev.org/openstack/cyborgBlueprints:https://blueprints.launchpad.net/openstack-cyborgBugs:https://bugs.launchpad.net/openstack-cyborgDocumentation:https://docs.openstack.org/cyborg/latest/Release notes:https://docs.openstack.org/releasenotes/cyborg/Design specifications:https://specs.openstack.org/openstack/cyborg-specs/FeaturesREST API for basic accelerator life cycle managementGeneric driver for common accelerator support
Package: openstackdocstheme
Open Infrastructure Projects Sphinx ThemesTheme and extension support for Sphinx documentation that is published by
Open Infrastructure Foundation projects.OpenStack docs.openstack.org Sphinx ThemeTheme support for Sphinx documentation that is published to
docs.openstack.org and developer.openstack.org.Intended for use by OpenStackprojects governed by the Technical Committee.StarlingX docs.starlingx.io Sphinx ThemeTheme support for Sphinx documentation that is published to
docs.starlingx.io.Intended for use by StarlingXprojects governed by the Technical Steering Committee.ReferencesFree software: Apache License, Version 2.0Documentation:https://docs.openstack.org/openstackdocstheme/latest/Release notes:https://docs.openstack.org/releasenotes/openstackdocstheme/Source:https://opendev.org/openstack/openstackdocsthemeBugs:https://launchpad.net/openstack-doc-tools
Package: openstack-doc-tools
OpenStack Doc ToolsThis repository contains tools used by the OpenStack Documentation
project.For more details, see theOpenStack Documentation Contributor Guide.License: Apache License, Version 2.0Source:https://opendev.org/openstack/openstack-doc-toolsBugs:https://bugs.launchpad.net/openstack-doc-toolsPrerequisitesYou need to have Python 2.7 installed for using the tools.This package needs a few external dependencies including lxml. If you
do not have lxml installed, you can either install python-lxml or have
it installed automatically and build from sources. To build lxml from
sources, you need a C compiler and the xml and xslt development
packages installed.To install python-lxml, execute the following based on your
distribution.On Fedora, RHEL 7, and CentOS 7:$ yum install python-lxmlOn openSUSE:$ zypper in python-lxmlOn Ubuntu:$ apt-get install python-lxmlFor building from source,  install the dependencies of lxml.On Fedora, RHEL 7, and CentOS 7:$ yum install python-devel libxml2-devel libxslt-develOn openSUSE:$ zypper in libxslt-develOn Ubuntu:$ apt-get install libxml2-dev libxslt-dev
Package: openstack-governance
The repositoryhttps://opendev.org/openstack/governance/contains OpenStack Technical Committee reference documents and tracks
official resolutions voted by the committee. It also contains a
library for accessing some of the machine-readable data in the
repository.Directory structure:reference/Reference documents which need to be revised over time.
Some motions will just directly result in reference doc changes.resolutions/When the motion does not result in a change in a reference doc, it
can be expressed as a resolution.
Those must be named YYYYMMDD-short-name with YYYYMMDD being the
proposal date in order to allow basic sorting.goals/Documentation for OpenStack community-wide goals, organized by
release cycle. These pages will be updated with project status
info over time, and if goals are revised.Seehttps://governance.openstack.org/tc/for details.
Package: openstack-heat
Team and repository tagsHeatHeat is a service to orchestrate multiple composite cloud applications using
templates, through both an OpenStack-native REST API and a
CloudFormation-compatible Query API.Why heat? It makes the clouds rise and keeps them there.Getting StartedIf you’d like to run from the master branch, you can clone the git repo:git clonehttps://opendev.org/openstack/heatDocumentation:https://docs.openstack.org/heat/latestTemplate samples:https://opendev.org/openstack/heat-templatesAgents:https://opendev.org/openstack/heat-agentsRelease Notes:https://docs.openstack.org/releasenotes/heat/Python clientDocumentation:https://docs.openstack.org/python-heatclient/latestSource:https://opendev.org/openstack/python-heatclientReport a Story (a bug/blueprint)If you’d like to report a Story (we used to call a bug/blueprint), you can
report it under Report a story inHeat’s StoryBoard.
If you must report the story under other sub-project of heat, you can find
them all inHeat StoryBoard Group.
if you encounter any issue.Referenceshttps://docs.amazonwebservices.com/AWSCloudFormation/latest/APIReference/API_CreateStack.htmlhttps://docs.amazonwebservices.com/AWSCloudFormation/latest/UserGuide/create-stack.htmlhttps://docs.amazonwebservices.com/AWSCloudFormation/latest/UserGuide/aws-template-resource-type-ref.htmlhttps://www.oasis-open.org/committees/tc_home.php?wg_abbrev=toscaWe have integration withhttps://opendev.org/openstack/python-novaclient(instance)https://opendev.org/openstack/python-keystoneclient(auth)https://opendev.org/openstack/python-swiftclient(object storage)https://opendev.org/openstack/python-neutronclient(networking)https://opendev.org/openstack/python-aodhclient(alarming service)https://opendev.org/openstack/python-cinderclient(block storage)https://opendev.org/openstack/python-glanceclient(image service)https://opendev.org/openstack/python-troveclient(database as a Service)https://opendev.org/openstack/python-saharaclient(hadoop cluster)https://opendev.org/openstack/python-barbicanclient(key management service)https://opendev.org/openstack/python-designateclient(DNS service)https://opendev.org/openstack/python-magnumclient(container service)https://opendev.org/openstack/python-manilaclient(shared file system service)https://opendev.org/openstack/python-mistralclient(workflow service)https://opendev.org/openstack/python-zaqarclient(messaging service)https://opendev.org/openstack/python-monascaclient(monitoring service)https://opendev.org/openstack/python-zunclient(container management service)https://opendev.org/openstack/python-blazarclient(reservation service)https://opendev.org/openstack/python-octaviaclient.git(Load-balancer service)https://opendev.org/openstack/python-senlinclient(Clustering service)https://opendev.org/openstack/python-vitrageclient.git(RCA service)https://opendev.org/openstack/python-ironicclient(baremetal provisioning service)
Package: openstacki18n
OpenStack I18nInternationalization (I18n) is essential to make OpenStack ubiquitous.
The mission of OpenStack I18n team is to make OpenStack
ubiquitously accessible to people of all language backgrounds,
by enhancing OpenStack software internationalization,
providing translation, maintaining a translation platform and
managing translation process for better quality of outcomes.About this repositoryThis repository maintains useful assets for the I18n team,
including the contribution guide, the terminologies and so on.Getting in touchMailing ListWe useopenstack-i18n@lists.openstack.orgas the mailing list.IRCWe all hang out on #openstack-i18n IRC channel on freenode.Team MeetingWe have a bi-weeklymeetingon Thursdays at alternating times.
Package: openstackinabox
Stack-In-A-Box-based OpenStack Services for use with Testing FramesworksOverviewStack-In-A-Boxprovides the ability to use mocked RESTful APIs naturally inside unit tests by using modules such asHTTPrettyorRequests-Mock.OpenStack-In-A-Boxprovides a series of mocked OpenStack Services inside theStack-In-A-Boxframework, thus providing a reliable mock-up of the OpenStack Services that can be utilized by applications written against them.InstallingInstallation is simple:pipinstallopenstackinaboxGoalsEnable Python modules to be unit tested against OpenStack services in an environment controlled by the unit tests.Provide reliable, accurate mock-ups of the servicesEnable unit testing to not have to mock the various tools, e.g KeystoneClient API, to perform their tests.Support both Positive and Negative testingTesting should be easy to do:you should not necessarily need to know the ins and outs of each serviceyou should be able to register what you need (f.e authenticaiton, storage) and have it just workshould be usable on systems like Travis (https://travis-ci.org/)should be light on requirementswe do not want to bloat your testing to fit our needsif we have many requirements they could interfere with your requirementsThe code being unit-tested should not be able to tell the difference of whether it is working withOpenStack-In-A-Boxor the real thingthere should be nothing special about setting up the testif you don’t turn on OpenStack-In-A-Box (andStack-In-A-Boxupon which it is built) then the code should be able to call the real thingcaveat: the utility tools (f.e httpretty, requests-mock) will determine the URL for the services being provided; seeStack-In-A-Boxfor details.Why not use framekwork X?This is a natural extension ofStack-In-A-Boxto provide OpenStack services to the unit testing being done. If you are usingStack-In-A-Boxthen it makes sense to also useOpenStack-In-A-Boxas it is simply providing a compatible set of OpenStack services that simply need to be registered withStack-In-A-Box.What’s Provided?Current work is on supporting the OpenStack Keystone v2 services. See the Issues and Milestone for more details.Working with FrameworksOpenStack-In-A-Boxbuilds onStack-In-A-Box. Simply instantiate the desired service and register it withStack-In-A-Box.ReferencesStack-In-A-Box-https://github.com/TestInABox/stackInABox/OpenStack-https://www.openstack.org/OpenStack Keystone-http://docs.openstack.org/developer/keystone/
Package: openstackinfo
OpenStack InfoGets information about what is in an OpenStack tenant.InstallationPrerequisites: - python >= 3.6The tool can be installed from PyPi:pipinstallopenstackinfoBleeding edge versions can be installed directly from GitHub:gitclonehttps://github.com/wtsi-hgi/openstack-info.gitcdopenstack-tenant-cleanerpythonsetup.pyinstallor using pip:pipinstallgit+https://github.com/wtsi-hgi/openstack-info.git@master#egg=openstackinfoUsageCLISet environment variables:exportOS_USERNAME=userexportOS_TENANT_NAME=tenantexportOS_AUTH_URL=http://example.com:5000/v2.0/exportOS_PASSWORD=passwordThen call:openstackinfoThe available options can be found withopenstackinfo-h:usage: openstackinfo [-h] [-i {type,id}] [--max-connections MAX_CONNECTIONS]
                     [--retries RETRIES] [--retry-wait RETRY_WAIT]
                     [--retry-wait-multiplier RETRY_WAIT_MULTIPLIER]

Openstack tenant information retriever

optional arguments:
  -h, --help            show this help message and exit
  -i {type,id}, --index {type,id}
                        What the OpenStack information should be index by
                        (default: type)
  --max-connections MAX_CONNECTIONS
                        Maximum number of simultaneous connections to make to
                        OpenStack. Configured automatically if not set
                        (default: None)
  --retries RETRIES     Number of times to retry getting information about a
                        particular tpye of OpenStack resource (default: 3)
  --retry-wait RETRY_WAIT
                        Initial amount of time (in seconds) to wait after a
                        failure before retrying (default: 1.0)
  --retry-wait-multiplier RETRY_WAIT_MULTIPLIER
                        Multiplier that is applied to the wait time after each
                        failure. e.g. An initial wait time of 1.0s, a wait
                        multiplier of 5.0, and a maximum of 3 retries will
                        result in the waits between retries of [1.0s, 5.0s,
                        25.0s] (default: 5.0)
  --retry-wait-deviation RETRY_WAIT_DEVIATION
                        To minimise collisions, the wait time before retrying
                        a request is randomised to plus or minus the value of
                        this parameter as a percentage of the total wait time.
                        e.g. A wait time of 1.0s and max deviation percentage
                        of 10.0 will result in an actual wait between 0.9s and
                        1.1s (default: 10.0)Pythonfromopenstackinfo.retriever.modelsimportCredentialsfromopenstackinfo.retriever.retrieversimportShadeInformationRetrieverfromopenstackinfo.helpersimportget_information,RunConfigurationfromopenstackinfo.indexersimportInformationIndexerByTyperetriever=ShadeInformationRetriever(credentials=Credentials(username,password,auth_url,tenant))configuration=RunConfiguration(retriever=retriever,indexer=InformationIndexerByType)openstack_info=get_information(configuration)Alternativesshade(underlying library:
no CLI, no re-indexing).Nova
CLI(does not return JSON).Openstack
CLI(does not return server metadata).
Package: openstack-magnum
Magnum is an OpenStack project which offers container orchestration engines
for deploying and managing containers as first class resources in OpenStack.For more information, please refer to the following resources:Free software:under theApache licenseDocumentation:http://docs.openstack.org/developer/magnumSource:http://git.openstack.org/cgit/openstack/magnumBlueprints:https://blueprints.launchpad.net/magnumBugs:http://bugs.launchpad.net/magnumREST Client:http://git.openstack.org/cgit/openstack/python-magnumclient
Package: openstack-member-spammer-estimator
OpenStack Member Spammer DetectorDependencies$ sudo apt update
$ sudo apt install python3-pip python3-dev build-essential libssl-dev libffi-dev python3-setuptools python3-venv 
libmysqlclient-devVirtual Env$python3.6-mvenvenv

$sourceenv/bin/activate

$pipinstall-rrequirements.txt
Package: openstack-mentoring-scripts
Python scripts for openstack-mentoring=======================These scripts work on the google docs spreadsheets.  Come to the mentoring meetingsif you want access to the spreadsheets.  More information on mentoring, sponsored bythe Women of OpenStack is here: https://wiki.openstack.org/wiki/Mentors----These scripts will match mentors and mentees and will generate a few types of emails:One is for when a match is found, it gives the mentor and mentee information andexplains the reasons for the match.One is for when a match is not found, it gives the mentee hope that a match will befound.The last is when a mentee has not given enough information to find a match, that isthere is no information in goal or area of interest to generate a match for them.
Package: openstack.nose_plugin
openstack.nose_plugin provides a nose plugin that allow’s nosetests output to
mimic the output of openstack’s run_tests.py.Installationpip install openstack.nose_pluginUsageThe following options are availible:--with-openstackEnable plugin Openstack: Nova style output
generator
[NOSE_WITH_OPENSTACK]--openstack-red=OPENSTACK_REDColorize run times greater than value red.
[NOSE_OPENSTACK_RED] or 1.0--openstack-yellow=OPENSTACK_YELLOWColorize run times greater than value yellow.
[NOSE_OPENSTACK_RED] or 0.25--openstack-show-elapsedShow the elaped runtime of tests.
[NOSE_OPENSTACK_SHOW_ELAPSED]--openstack-colorColorize output. [NOSE_OPENSTACK_COLOR]--openstack-nocolorDisable colorize output. [NOSE_OPENSTACK_COLOR]--openstack-num-slow=OPENSTACK_NUM_SLOWNumber top slowest tests to report.
[NOSE_OPENSTACK_NUM_SLOW]
Package: openstack-placement
If you are viewing this README on GitHub, please be aware that placement
development happens onOpenStack gitandOpenStack
gerrit.OpenStack PlacementOpenStack Placement provides an HTTP service for managing, selecting,
and claiming providers of classes of inventory representing available
resources in a cloud.APITo learn how to use Placement’s API, consult the documentation available
online at:Placement API ReferenceFor more information on OpenStack APIs, SDKs and CLIs in general, refer to:OpenStack for App DevelopersDevelopment resources for OpenStack cloudsOperatorsTo learn how to deploy and configure OpenStack Placement, consult the
documentation available online at:OpenStack PlacementIn the unfortunate event that bugs are discovered, they should be reported to
the appropriate bug tracker. If you obtained the software from a 3rd party
operating system vendor, it is often wise to use their own bug tracker for
reporting problems. In all other cases use the master OpenStack bug tracker,
available at:Bug TrackerFile new BugDevelopersFor information on how to contribute to Placement, please see the contents of
CONTRIBUTING.rst.Further developer focused documentation is available at:Official Placement Documentation
Package: openstack-publicdns
OpenStack public DNS pluginsThis package provides a collection of plugins to simplify the use of
public DNS names for OpenStack virtual machine instances.Each OpenStack network can have a configureddns_domain.  Virtual
machine instances launched within that network will have a hostname
constructed from the network'sdns_domainand appropriate DNS
records will be created automatically.For example: if an instance namedtestvmis launched in a network
with the DNS domainexample.orgthen the instance will be given the
DHCP hostnametestvm.example.organd the DNS A and AAAA records fortestvm.example.orgwill be added to the DNS zone.InstallationThe easiest approach is to install the prebuilt RPM from theCOPR
repository.ConfigurationIn/etc/neutron/plugin.iniin the[ml2]section, change theextension_driverslist to includepublicdnsinstead ofdns_domain_ports(ordns).  For example:[ml2]extension_drivers=port_security,publicdnsIn/etc/neutron/dhcp_agent.iniin the[DEFAULT]section, changedhcp_driverfromneutron.agent.linux.dhcp.Dnsmasqtoopenstack_publicdns.neutron.dhcp.Dnsmasq.  For example:[DEFAULT]dhcp_driver=openstack_publicdns.neutron.dhcp.DnsmasqIn/etc/designate/designate.conf, in the[service:central]section, changestorage_driverfromsqlalchemytopublicdns.
For example:[service:central]storage_driver=publicdns
Package: openstacksdk-plugin
OpenStack SDK Example PluginThis repository contains an example OpenStack SDK plugin that you can use to
create your own plugin.  Just fork the repository or copy it if you like.
The most important part are the entry points.To try out the example plugin, install the package and run the following:openstacksdkThe script loads the example plugin and calls the two methods of the
proxy.Free software: Apache licenseDocumentation:http://docs.openstack.org/developer/openstacksdk-pluginSource:http://git.openstack.org/cgit/openstack/openstacksdk-pluginBugs:http://bugs.launchpad.net/python-openstacksdkTODOWrite docs describing how to make a pluginFix this README with proper links to source and documentation
Package: openstack-summit-counter
Thesummit countplugin for python-openstackclient helps the user
determine the number of summits they have attended since the beginning
of their interaction with OpenStack.Installing$ pip install openstack-summit-counterUsing$ openstack summit count $first [$current]For example, if your first summit was for the “Folsom” series and the
next summit is for “Rocky”:$ openstack summit count folsom rocky

+---------+-------+
| Field   | Value |
+---------+-------+
| Summits | 13    |
+---------+-------+Can also be used for counting PTGs. For example:$ openstack ptg count pike rocky

+-------+-------+
| Field | Value |
+-------+-------+
| PTGs  | 3     |
+-------+-------+
Package: openstack-valet
# ValetValet is a cloud resource placement optimization service. Valet gives OpenStack the ability to optimize cloud resources while simultaneously meeting a cloud application’s QoS requirements. Through model driven orchestration, the target state of Valet is to provide “holistic OpenStack data-plane resource placement”. Valet provides an api service, a placement optimizer (Ostro), a high availability data storage and persistence layer (Music), and a set of OpenStack plugins.## Why Valet exists:For large-scale, multi-tenant cloud operators, there is a large demand for tenant specific service requests.  This demand drives the growth of the number of cloud availability zones and compartmentalization of the cloud, which then leads to increased provisioning and sub-optimal use of cloud and staff resources.  Also, security requirements lead us to place specialized network appliances of these tenants separately into “exclusive” hosts that do not have internet connectivity.Valet responds to the challenges outlined above by enhancing OpenStack Nova scheduling to develop resource management optimization.  By planning the placement of all the cloud resources for an application in a holistic manner, there is opportunity to reduce cross-rack traffic, reduce resource fragmentation, and save on operating costs.## Learn more about Valet:[OpenStack Newton Summit Presentation](https://www.openstack.org/videos/video/valet-holistic-data-center-optimization-for-openstack) (Austin, TX, 27 April 2016)[Presentation Slides](http://www.research.att.com/export/sites/att_labs/techdocs/TD_101806.pdf) (PDF)## Valet consists of the following components:[valet-openstack](https://github.com/att-comdev/valet/blob/master/doc/valet_os.md): a set of OpenStack plugins used to interact with Valet[valet-api](https://github.com/att-comdev/valet/blob/master/doc/valet_api.md): an API engine used to interact with Valet[Ostro](https://github.com/att-comdev/valet/blob/master/doc/ostro.md): a placement optimization engine[ostro-listener](https://github.com/att-comdev/valet/blob/master/doc/ostro_listener.md): a message bus listener used in conjunction with Ostro and Music## Additional documents:[OpenStack Heat Resource Plugins](https://github.com/att-comdev/valet/blob/master/valet_plugins/valet_plugins/heat/README.md): Heat resources[Placement API](https://github.com/att-comdev/valet/blob/master/doc/valet_api.md): API requests/responses[Using Postman with valet-api](https://github.com/att-comdev/valet/blob/master/valet/tests/api/README.md): Postman support## License:Valet is distributed under the terms of the Apache License, Version 2.0. The full terms and conditions of this license are detailed in the LICENSE file.