| 2016-05-09 21:27:27 |
Assaf Muller |
description |
To provide the support for running connectivity tests between the vms of a tenant, from a centralized management system so that troubleshooting the environment becomes easier.
Problem Description
===================
Currently there is no automated system which can manage and monitor the connectivity of the resources in a tenant's environment. At the moment, this is achieved by manually executing the connectivity tests. This blueprint proposes the automation of this management and monitoring process.
Proposed Change
===============
- A new feature will be added which will allow the tenant admin user to test its environment (for eg. ping or tracert).
- This functionality will also be provided from openstack dashboard to drag and drop the vms to be tested.
- Only Admin user will be allowed to execute the testcases for the connectivity.
New APIs will be added to support the execution of the Connectivity management tests via the centralized management system to allow cli execution of the tests and also for integrating the functionality into horizon.
Advantage
=========
This change will allow operators/admin users to quickly check the status of all the VMs in the network and troubleshooting the problems. |
To provide the support for running connectivity tests between the vms of a tenant, from a centralized management system so that troubleshooting the environment becomes easier.
Problem Description
===================
Currently there is no automated system which can manage and monitor the connectivity of the resources in a tenant's environment. At the moment, this is achieved by manually executing the connectivity tests. This blueprint proposes the automation of this management and monitoring process.
Proposed Change
===============
- A new feature will be added which will allow the tenant admin user to test its environment (for eg. ping or tracert).
- Only Admin user will be allowed to execute the testcases for the connectivity.
New APIs will be added to support the execution of the Connectivity management tests via the centralized management system to allow cli execution of the tests and also for integrating the functionality into horizon.
Advantage
=========
This change will allow operators/admin users to quickly check the status of all the VMs in the network and troubleshooting the problems.
Spec
====
https://review.openstack.org/#/c/308973/ |
|
| 2016-05-10 04:47:07 |
Hynek Mlnarik |
description |
To provide the support for running connectivity tests between the vms of a tenant, from a centralized management system so that troubleshooting the environment becomes easier.
Problem Description
===================
Currently there is no automated system which can manage and monitor the connectivity of the resources in a tenant's environment. At the moment, this is achieved by manually executing the connectivity tests. This blueprint proposes the automation of this management and monitoring process.
Proposed Change
===============
- A new feature will be added which will allow the tenant admin user to test its environment (for eg. ping or tracert).
- Only Admin user will be allowed to execute the testcases for the connectivity.
New APIs will be added to support the execution of the Connectivity management tests via the centralized management system to allow cli execution of the tests and also for integrating the functionality into horizon.
Advantage
=========
This change will allow operators/admin users to quickly check the status of all the VMs in the network and troubleshooting the problems.
Spec
====
https://review.openstack.org/#/c/308973/ |
To enable operators to reduce manual work upon experiencing networking
issue, and to fast pinpoint the cause of a failure, there is a need for
neutron to provide real-time diagnostics of its resources. This way,
current need for manual checks, often requiring root access, would be
gradually replaced by API queries. Providing diagnostics options in
neutron API would also open space for development of specialized tools
that would solve particular type of issues, e.g. inability to ping VM’s
interface.
Note: The description of this RFE was changed to cover previous RFEs
related to diagnostics (namely bug 1563538, bug 1537686, bug 1519537
and the original of this bug).
Problem Description
===================
One of common questions seen at ask.openstack.org and mailing lists is
"Why cannot I ping my floating IP address?". Usually, there are common
steps in the diagnostics required to answer the question involving
determination of relevant namespaces, pinging the instance from that
namespaces etc. Currently, these steps need to be performed manually,
often by crawling the relevant hosts and running tools that require root
access.
Neutron currently provides data on how the resources *should* be
configured. It however provides only a very little diagnostics
information reflecting *actual* resource state. Hence if an issue
occurs, user is often left with only a little details of what works and
what not, and has to manually crawl affected hosts to troubleshoot the
issue.
Proposed Change
===============
This RFE requests an extension of current API that exposes
diagnostics for neutron resources so that it is accessible via API
calls, reducing amount of needed manual work. Further it describes
additions to Neutron CLI necessary to call the newly added API.
Spec
====
https://review.openstack.org/#/c/308973/ |
|
