[GitHub] PaulAngus closed pull request #4: Add run diagnostics to admin guide and new apis
PaulAngus closed pull request #4: Add run diagnostics to admin guide and new apis URL: https://github.com/apache/cloudstack-documentation/pull/4 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of provenance: As this is a foreign pull request (from a fork), the diff is supplied below (as it won't show otherwise due to GitHub magic): diff --git a/source/_static/images/diagnostics-form.png b/source/_static/images/diagnostics-form.png new file mode 100644 index 000..a9b0b37 Binary files /dev/null and b/source/_static/images/diagnostics-form.png differ diff --git a/source/_static/images/run-diagnostics-icon.png b/source/_static/images/run-diagnostics-icon.png new file mode 100644 index 000..61e2aac Binary files /dev/null and b/source/_static/images/run-diagnostics-icon.png differ diff --git a/source/adminguide/systemvm.rst b/source/adminguide/systemvm.rst index 286e5e4..4c3da98 100644 --- a/source/adminguide/systemvm.rst +++ b/source/adminguide/systemvm.rst @@ -552,3 +552,44 @@ The administrator can log in to the secondary storage VM if needed. :alt: Updating Console Proxy SSL Certificate .. |vr-upgrade.png| image:: /_static/images/vr-upgrade.png :alt: Button to upgrade VR to use the new template. + +Troubleshoot networks from System VMs +- +.. |run-diagnostics-icon.png| image:: /_static/images/run-diagnostics-icon.png +.. |diagnostics-form.png| image:: /_static/images/diagnostics-form.png + +For troubleshooting of network issues in CloudStack hosted networks, CloudStack allows +the administrator to execute network-utility commands (ping, traceroute or arping) +remotely on system VMs. + +To run either a ping, traceroute or arping through the CloudStack UI: + +#. As an administrator, log in to the CloudStack UI. + +#. Navigate to Infrastructure > System VMs or Virtual Routers. + +#. Click on the Run Diagnostics button. |run-diagnostics-icon.png| + +#. A form will pop up similar to this; + |diagnostics-form.png| +#. Fill in the details and click OK. + +The Extra Args parameter is for specifying command line optional parameters +as one would when executing any of the tools from the terminal or command line. + +The supported versions are Debian 9 based since system VMs are built using the +same Debian 9 based templates. + +| See: +| Traceroute(1): https://manpages.debian.org/stretch/traceroute/traceroute.1.en.html +| Ping(8): https://manpages.debian.org/stretch/iputils-ping/ping.8.en.html +| Arping(8): https://manpages.debian.org/stretch/arping/arping.8.en.html + + +Non-Alphanumeric characters (metacharacters) are not allowed for this parameter +except for the “-“ and the “.”. Any metacharacter supplied will immediately result +in an immediate termination of the command and report back to the operator that an illegal character was passed + + + + diff --git a/source/releasenotes/api-changes.rst b/source/releasenotes/api-changes.rst index b666b39..ea0ec1f 100644 --- a/source/releasenotes/api-changes.rst +++ b/source/releasenotes/api-changes.rst @@ -118,7 +118,8 @@ New API Commands +-++ | ``releasePodIpAddress`` | Releases a Pod IP back to the Pod | +-++ - +| ``runDiagnostics`` | Run network-utility commands remotely on system VMs| ++-++ Parameters Changed API Commands --- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] PaulAngus closed pull request #5: documentation for destroyVM also removes volumes
PaulAngus closed pull request #5: documentation for destroyVM also removes volumes URL: https://github.com/apache/cloudstack-documentation/pull/5 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of provenance: As this is a foreign pull request (from a fork), the diff is supplied below (as it won't show otherwise due to GitHub magic): diff --git a/source/adminguide/virtual_machines.rst b/source/adminguide/virtual_machines.rst index f8c34de..eda2b7c 100644 --- a/source/adminguide/virtual_machines.rst +++ b/source/adminguide/virtual_machines.rst @@ -827,6 +827,8 @@ To delete a virtual machine: #. Click the Destroy Instance button. |Destroyinstance.png| +#. Optionally both expunging and the deletion of any attached volumes can be enabled. + Working with ISOs - diff --git a/source/releasenotes/api-changes.rst b/source/releasenotes/api-changes.rst index b666b39..649d241 100644 --- a/source/releasenotes/api-changes.rst +++ b/source/releasenotes/api-changes.rst @@ -1006,4 +1006,12 @@ Parameters Changed API Commands | | - ``name`` | | | | +-++ +| ``destroyVirtualMachine`` | **Request:** | +| | | +| | *New Parameters:* | +| | | +| | - ``volumeids`` | +| | | ++-++ + This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
Re: VRs swapping with 256 MB RAM
Hi Just to clarify, we had 256 MB in our lab only. The prod VRs have 1 GB RAM and 4 CPUs, 1 CPU per network interface for optimal performance + 1 for the OS. Regards René On 09/20/2018 02:35 PM, Rakesh Venkatesh wrote: > Hello Rene > > Even for VR's running on KVM, 256MB is really less. Thats why we offer > extra VR with 2 cores and 1GB RAM as another option so that customers can > use it instead of the default 256MB and 1 core. > > On Tue, Sep 18, 2018 at 5:56 PM Rene Moser wrote: > >> Hi >> >> While running test for a 4.11.1 (VMware) upgrade in our lab, we run into >> low memory / swapping of VRs having 256 MB RAM. After 2-3 days it became >> critical because the management server connections to VRs took very >> long, minutes, this resulted in many more problems all over. >> >> Make sure your VRs have enough RAM. >> >> Regards >> René >> > >
CloudStack Collab in Brazil
Hello fellow devs and users (pardon me for the cross post), I already contacted the PMC on this matter, and I am now opening the discussion to the whole community. Let’s see what you guys think about a CloudStack conference in Brazil, and let’s work to make it happen ;) Since the rather shameful? situation with the CloudStack Collab Conference (CCC) in Brazil last year, I have been looking for possible ways to enable the event. And, it seems that I found it, and it is something that we are already used to do. There is a conference series in Brazil called TDC (The Developer’s conference) [1]. They run three conferences a year (Florianopolis, São Paulo, and Porto Alegre). They have been running for over a decade now. I attended the last one in São Paulo (July 2018) and it was awesome. To give you guys some numbers for the São Paulo event: - 4524 attendants - 6040 online-viewers (some talks are live streamed) - 2927 corporate registrations - 63 different tracks, and more than 300 talks. - 5 days of conference (Tuesday-Saturday) They are in the process of internationalizing the conference now. The hot site is being translated, and they are preparing things for English/Spanish CFPs and tracks. While talking with one of the organizers during the event, I mentioned that we have been doing collocated CCC with ApacheCon and that I would love to see CCC in Brazil. Ant it turns out, they would love to see us there in Brazil as well. They offered to provide the same support as ApacheCon provides us. We would only need to organize the CFP and selection of the presentations. We would also need to tell them our needs: rooms, hackathon spaces, and so on. They are proposing for us space in their Florianopolis TDC 2019, which will be held in Florianopolis city. The event will take place in April 2019 (there is not a possibility for the event to be canceled this time!). I can coordinate this process with them, but I might need some help from you guys. That is why I would like to discuss this option here first. What do you think about the best dates to run a CCC in Brazil? They have an event in April, other in Jully, and the last one in December. In theory, we can discuss and try to get approval to some other city/date, but they recommended Florianopolis/April event. (We talked about this on the PMC list, and it seems that for an international audience, the April date looks the best one). Also, would some of you be willing to attend? I think the presence of committers/PMCs is vital to meet face to face with the community that uses CloudStack there. And of course, the event is way broader than Apache and CloudStack. Therefore, we can show ourselves and hopefully attract new people/companies. I am eager to hear your feedback guys ;) [1] http://www.thedevelopersconference.com.br/en -- Rafael Weingärtner
[GitHub] houthuis commented on issue #5: documentation for destroyVM also removes volumes
houthuis commented on issue #5: documentation for destroyVM also removes volumes URL: https://github.com/apache/cloudstack-documentation/pull/5#issuecomment-423484456 @PaulAngus rewording change made This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
