Why Gemfury?
Push, build, and install
RubyGems
npm packages
Python packages
Maven artifacts
PHP packages
Go Modules
Debian packages
RPM packages
NuGet packages
triliodata-3-3 / python3-dmapi deb
Repository URL to install this package:
|
Version:
3.3.35 ▾
|
python3-dmapi
/
usr
/
lib
/
python3
/
dist-packages
/
dmapi
/
cmd
/
__pycache__
/
status.cpython-35.pyc
|
|---|
çáþ\Vs ã @ sc d Z d d l m Z d d l Z d d l Z d d l Z d d l Z d d l Z d d l Z d d l m
Z d d l m
Z
d d l m Z d d l Z d d l Z d d l m Z d d l m Z m Z m Z m Z d d l m Z d d
l m Z d d l Z d d l m Z d d l m! Z" d d
l# m$ Z% d d l& m' Z' d d l( m) Z* d d l( m+ Z+ d d l m, Z, d d l m- Z- e j. j/ Z/ d Z0 Gd d d e j1 Z2 e2 j3 e' d e2 j4 e' d e2 j5 e' d i Z6 Gd d d e7 Z8 Gd d d e7 Z9 d e9 i Z: e j; e j< d e: Z< e
j= d d d! d" d# d$ e< Z> d% d& Z? d S)'z)
CLI interface for nova status commands.
é )Úprint_functionN)Ú
exceptions)Úcfg)Ú jsonutils)Úfunc)ÚMetaDataÚTableÚand_Úselect)Úfalse)Úcommon)Úconfig)Úcontext)Úapi)Ú_)Ú cell_mapping)Úfields)Úutils)Úversionz:https://docs.openstack.org/nova/latest/user/placement.htmlc @ s( e Z d Z d Z d Z d Z d Z d S)ÚUpgradeCheckCodezjThese are the status codes for the nova-status upgrade check command
and internal check commands.
r é é N)Ú__name__Ú
__module__Ú __qualname__Ú__doc__ÚSUCCESSÚWARNINGÚFAILURE© r r ú2/usr/lib/python3/dist-packages/dmapi/cmd/status.pyr , s r ZSuccessÚWarningZFailurec s+ e Z d Z d Z d f d d Z S)ÚUpgradeCheckResultaT Class used for 'nova-status upgrade check' results.
The 'code' attribute is an UpgradeCheckCode enum.
The 'details' attribute is a translated message generally only used for
checks that result in a warning or failure code. The details should provide
information on what issue was discovered along with any remediation.
Nc s) t t | j | | _ | | _ d S)N)Úsuperr" Ú__init__ÚcodeÚdetails)Úselfr% r& )Ú __class__r r r$ N s zUpgradeCheckResult.__init__)r r r r r$ r r )r( r r" E s r" c @ s e Z d Z d Z d d d Z d d Z e d d Z d d
Z e d d Z e d
d Z
d d Z e d d Z d d Z
d d Z d d Z e d e f e d e f e d e f e d e
f e d e f f Z d d Z d d! Z d S)"ÚUpgradeCommandsa Commands related to upgrades.
The subcommands here must not rely on the nova object model since they
should be able to run on n-1 data. Any queries to the database should be
done through the sqlalchemy query language directly like the database
schema migrations.
Nc C sR t d t j d | } t d | d d } t t j g j | j S)z9Returns the number of compute nodes in the cell database.Úbindr Ú
compute_nodesÚautoloadT) r Ú
db_sessionÚ
get_enginer r
ÚsqlfuncÚcountÚ select_fromÚscalar)r' r Úmetar+ r r r Ú_count_compute_nodes] s z$UpgradeCommands._count_compute_nodesc C s t } t j | _ t d | d d } t t j g j | j } | d k ry t
d } t t j
| St t j g j | j | j j t j j k j } | d k rà t
d } t t j
| St d | d d } t t j g j | j } | d k ru| j } | d k rYt
d
} t t j
| St
d } t t j | St t j S) aD Checks to see if cells v2 has been setup.
These are the same checks performed in the 030_require_cell_setup API
DB migration except we expect this to be run AFTER the
nova-manage cell_v2 simple_cell_setup command, which would create the
cell and host mappings and sync the cell0 database schema, so we don't
check for flavors at all because you could create those after doing
this on an initial install. This also has to be careful about checking
for compute nodes if there are no host mappings on a fresh install.
Ú
cell_mappingsr, Tr zThere needs to be at least two cell mappings, one for cell0 and one for your first cell. Run command 'nova-manage cell_v2 simple_cell_setup' and then retry.r z[No cell0 mapping found. Run command 'nova-manage cell_v2 simple_cell_setup' and then retry.Ú
host_mappingsr zwNo host mappings found but there are compute nodes. Run command 'nova-manage cell_v2 simple_cell_setup' and then retry.zNo host mappings or compute nodes were found. Remember to run command 'nova-manage cell_v2 discover_hosts' when new compute hosts are deployed.)r r- Úget_api_enginer* r r
r/ r0 r1 r2 r r" r r ÚwhereÚcÚuuidÚcell_mapping_objÚ CellMappingÚ
CELL0_UUIDr4 r )r' r3 r5 r0 Úmsgr6 Ú num_computesr r r Ú_check_cellsv2r s. $ $ z UpgradeCommands._check_cellsv2c C s" t j d } | j | j S)zDo an HTTP get call against placement engine.
This is in a dedicated method to make it easier for unit
testing purposes.
Z placement)r Zget_ksa_adapterÚgetÚjson)ÚpathÚclientr r r Ú_placement_get© s z UpgradeCommands._placement_getc C sv yu | j d } t j | d d d } t j d } | | k rt t d d | d | i } t t j | SWnñ t j k
r¨ t d } t t j | SYnÁ t j k
rØ t d
} t t j | SYn t j
k
rt d } t t j | SYna t j k
r8t d } t t j | SYn1 t j k
rht d
} t t j | SYn Xt t j
S)zÑChecks to see if the placement API is ready for scheduling.
Checks to see that the placement API service is registered in the
service catalog and that we can make requests against it.
ú/Úversionsr Ú max_versionz1.17z>Placement API version %(needed)s needed, you have %(current)s.ÚneededÚcurrentz8No credentials specified for placement API in nova.conf.z*Placement service credentials do not work.z!Placement API endpoint not found.z'Discovery for placement API URI failed.z*Placement API does not seem to be running.)rE Ú
pkg_resourcesÚ
parse_versionr r" r r Úks_excZMissingAuthPluginÚ UnauthorizedZEndpointNotFoundZDiscoveryFailureZNotFoundr )r' rG rH Z
needs_versionr> r r r Ú_check_placement´ s2 z UpgradeCommands._check_placementc C s| t j j j t j j } t d t j } t d | d d } t t
j g j | j
| j j | k j S)a/ Returns the number of compute resource providers in the API database
The resource provider count is filtered based on resource providers
which have inventories records for the VCPU resource class, which is
assumed to only come from the ResourceTracker in compute nodes.
r* Ú inventoriesr, T)r Z
ResourceClassZSTANDARDÚindexZVCPUr r- r7 r r
r/ r0 r1 r8 r9 Zresource_class_idr2 )Z
vcpu_rc_idr3 rP r r r Ú!_count_compute_resource_providersÛ s z1UpgradeCommands._count_compute_resource_providersc C s[ t d t j } t d | d d } | j j | j j t j j
k j j S)z5Queries the API database for non-cell0 cell mappings.r* r5 r, T)
r r- r7 r r
r8 r9 r: r; r< r= ÚexecuteÚfetchall)r3 r5 r r r Ú_get_non_cell0_mappingsô s
z'UpgradeCommands._get_non_cell0_mappingsc C s/ | j } | j } t j } d } xI | D]5 } t j | | } | | j | 7} Wd QRXq1 W| j } | d k rà | d k rº t d d | d t i } t t j
| St d d t i } t t j | S| | k r t d d | d | d t i } t t j
| St t j Sd S)
aF Checks the status of resource provider reporting.
This check relies on the cells v2 check passing because it queries the
cells for compute nodes using cell mappings.
This check relies on the placement service running because if it's not
then there won't be any resource providers for the filter scheduler to
use during instance build and move requests.
Note that in Ocata, the filter scheduler will only use placement if
the minimum nova-compute service version in the deployment is >= 16
which signals when nova-compute will fail to start if placement is not
configured on the compute. Otherwise the scheduler will fallback
to pulling compute nodes from the database directly as it has always
done. That fallback will be removed in Pike.
r Na There are no compute resource providers in the Placement service but there are %(num_computes)s compute nodes in the deployment. This means no compute nodes are reporting into the Placement service and need to be upgraded and/or fixed. See %(placement_docs_link)s for more details.r? Zplacement_docs_linkzéThere are no compute resource providers in the Placement service nor are there compute nodes in the database. Remember to configure new compute nodes to report into the Placement service. See %(placement_docs_link)s for more details.a4 There are %(num_resource_providers)s compute resource providers and %(num_compute_nodes)s compute nodes in the deployment. Ideally the number of compute resource providers should equal the number of enabled compute nodes otherwise the cloud may be underutilized. See %(placement_docs_link)s for more details.Znum_resource_providersZnum_compute_nodes) rR rU Ú nova_contextÚget_admin_contextÚ target_cellr4 r ÚPLACEMENT_DOCS_LINKr" r r r )r' Znum_rpsr5 Úctxtr? r Úcctxtr> r r r Ú_check_resource_providersý s0
z)UpgradeCommands._check_resource_providersc C s | j j | j j | d k j j } t j | d d d } d | k rb | d n i } x! | D] } | j d ro d Sqo Wd S) Nr: ÚflavorÚcurznova_object.dataZ extra_specszresources:CUSTOM_TF) r
r8 r9 Z
instance_uuidrS Úfirstr ÚloadsÚ
startswith)ÚextrasÚinstÚextrar] ÚspecsZspec_keyr r r Ú _is_ironic_instance_migratedS s 1
z,UpgradeCommands._is_ironic_instance_migratedc s | j } t j } t j t x^| D]V} t j | | ;} t d t j d | } t
d | d d } | j j t
| j j d k | j j d k j j } | r}t
d | d d } t
d | d d } x | D] }
|
d
} | j j t
| j j | k | j j d k j j } x2 | D]* }
| j | |
sK | d d 7<qKWqò WWd
QRXq. W| sªt d } t t j | S røt d d j f d d t j D } t t j | St t j S)aE In Pike, ironic instances and flavors need to be migrated to use
custom resource classes. In ironic, the node.resource_class should be
set to some custom resource class value which should match a
"resources:<custom resource class name>" flavor extra spec on baremetal
flavors. Existing ironic instances will have their embedded
instance.flavor.extra_specs migrated to use the matching ironic
node.resource_class value in the nova-compute service, or they can
be forcefully migrated using "nova-manage db ironic_flavor_migration".
In this check, we look for all ironic compute nodes in all non-cell0
cells, and from those ironic compute nodes, we look for an instance
that has a "resources:CUSTOM_*" key in it's embedded flavor extra
specs.
r* r r+ r, TZironicr Ú instancesZinstance_extraZhypervisor_hostnamer: r NzBUnable to determine ironic flavor migration without cell mappings.z~There are (cell=x) number of unmigrated instances in each cell: %s. Run 'nova-manage db ironic_flavor_migration' on each cell.ú c 3 s# | ] } d | | f Vq d S)z(%s=%s)Nr )Ú.0Zcell_id)Ú!unmigrated_instance_count_by_cellr r ú <genexpr>§ s zAUpgradeCommands._check_ironic_flavor_migration.<locals>.<genexpr>) rU rV rW Ú collectionsÚ defaultdictÚintrX r r- r. r r
r8 r r9 Zhypervisor_typeÚdeletedrS rT Únoderf r r" r r ÚjoinÚsortedÚkeysr r )r' r5 rZ r r[ r3 r+ Z ironic_nodesrg rb rp ÚnodenameZironic_instancesrc r> r )rj r Ú _check_ironic_flavor_migrationc s@
$
$
" z.UpgradeCommands._check_ironic_flavor_migrationc C s t d t j d | } t d | d d } t t j | j j g j | j
t | j j | k | j j
d k | j j t k j S)Nr* r Úservicesr, Tr )r r- r. r r
r/ Úminr9 r r1 r8 r Úbinaryro Z forced_downr r2 )r' r rx r3 rv r r r Ú_get_min_service_version± s z(UpgradeCommands._get_min_service_versionc
C s3 t j j r t t j St d t j } t d | d d } | j
j j } | s} t
d } t t j | St j } g } xe | D]] } t j | | B } | j | d } | d k rì | d k rì | j | d Wd QRXq W| r&t
d
d j | } t t j | St t j S) aû Checks nova-osapi_compute service versions across cells.
For non-cellsv1 deployments, based on how the [database]/connection
is configured for the nova-api service, the nova-osapi_compute service
versions before 15 will only attempt to lookup instances from the
local database configured for the nova-api service directly.
This can cause issues if there are newer API service versions in cell1
after the upgrade to Ocata, but lingering older API service versions
in an older database.
This check will scan all cells looking for a minimum nova-osapi_compute
service version less than 15 and if found, emit a warning that those
service entries likely need to be cleaned up.
r* r5 r, Tz?Unable to determine API service versions without cell mappings.znova-osapi_computeNé r: aW The following cells have 'nova-osapi_compute' services with version < 15 which may cause issues when querying instances from the API: %s. Depending on how nova-api is configured, this may not be a problem, but is worth investigating and potentially cleaning up those older records. See https://bugs.launchpad.net/nova/+bug/1759316 for details.z, )ÚCONFÚcellsÚenabler" r r r r- r7 r r
rS rT r r rV rW rX ry Úappendrq )
r' r3 r5 Zmappingsr> rZ Zcells_with_old_api_servicesÚmappingr[ Ú min_versionr r r Ú_check_api_service_versionº s*
z*UpgradeCommands._check_api_service_versionzCells v2z
Placement APIzResource ProviderszIronic Flavor MigrationzAPI Service Versionc C s5 | j d k r1 d j t j | j d d d Sd S)NÚ
é< Úsubsequent_indentz )r& rq ÚtextwrapÚwrap)r' Zupgrade_check_resultr r r Ú _get_details s z UpgradeCommands._get_detailsc C sñ t j } g } xN | j D]C \ } } | | } | j | | f | j | k r | j } q Wt j t d g d t j } d | _ xV | D]N \ } } t d d | d t
| j d | j | i } | j | g q Wt
| | S)a Performs checks to see if the deployment is ready for upgrade.
These checks are expected to be run BEFORE services are restarted with
new code. These checks also require access to potentially all of the
Nova databases (nova, nova_api, nova_api_cell0) and external services
such as the placement API service.
:returns: UpgradeCheckCode
zUpgrade Check ResultsZhrulesÚlz7Check: %(name)s
Result: %(result)s
Details: %(details)sÚnameÚresultr& )r r Ú_upgrade_checksr~ r% Ú prettytableZ PrettyTabler ZALLZalignÚUPGRADE_CHECK_MSG_MAPr Zadd_rowÚprint)r' Z return_codeZ
check_resultsr r r ÚtÚcellr r r Úcheck s$
zUpgradeCommands.check)r r r r r4 r@ Ú staticmethodrE rO rR rU r\ rf ru ry r r r r r r r r r r) T s& 7 ' V N D r) ÚupgradeÚ
categoriesÚcategoryÚtitlezCommand categoriesÚhelpzAvailable categoriesÚhandlerc C sÉ t j t t j t j t j j d k rC t t
j d St j j d k rf t j
t d Sy, t j \ } } } | | | } | SWn0 t k
rÄ t t d t j d SYn Xd S)z4Parse options and call the appropriate class/method.r r zbash-completionz Error:
%séÿ N)r{ Zregister_cli_optÚ category_optr
Ú
parse_argsÚsysÚargvr r r r Zversion_string_with_packageÚ
cmd_commonZprint_bash_completionÚ
CATEGORIESZ
get_action_fnÚ Exceptionr Ú tracebackÚ
format_exc)ÚfnZfn_argsZ fn_kwargsÚretr r r ÚmainT s
r¥ )@r Ú
__future__r rl ÚenumÚ functoolsr r
r¡ Z
keystoneauth1r rM Z oslo_configr Zoslo_serializationr rK r Z
sqlalchemyr r/ r r r r
Zsqlalchemy.sqlr Znova.cmdr r Z nova.confZnovar
r rV Znova.db.sqlalchemyr r- Z nova.i18nr Z nova.objectsr r; r r r Úconfr{ rY ÚIntEnumr r r r r Úobjectr" r) r ÚpartialZadd_command_parsersZ
SubCommandOptr r¥ r r r r Ú<module> sT " ÿ ó