[jira] [Commented] (CLOUDSTACK-10451) GSoC 2022 Idea: Instant Instance Deploy (using VM Definitions)

["Julia ida (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-10451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17517204#comment-17517204 ] 

Julia ida commented on CLOUDSTACK-10451:
----------------------------------------

h4. ion
Currently the QuorumCxnManager connectOne method dumps an exception when it encounters java.net.SocketTimeoutException: Read timed out, or java.net.ConnectException: Connection refused in addition to providing an error message.

As an example, the following output is seen:

[2020-01-20 00:21:23,828] WARN Cannot open channel to 3 at election address aaa-3/10.0.1.3:3888 (org.apache.zookeeper.server.quorum.QuorumCnxManager)
java.net.ConnectException: Connection refused (Connection refused)
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:607)
at org.apache.zookeeper.server.quorum.QuorumCnxManager.connectOne(QuorumCnxManager.java:558)
at org.apache.zookeeper.server.quorum.QuorumCnxManager.connectAll(QuorumCnxManager.java:610)
at org.apache.zookeeper.server.quorum.FastLeaderElection.lookForLeader(FastLeaderElection.java:838)

 

These exceptions are frequently output when launching and restarting several zookeeper servers and create confusion in what are normal operations and expected errors. I would suggest a few of these specific expected errors could be detected and reduced to only the text error output without the accompanying exception

When launching the first node in a 3 node quorum cluster, about 120 lines of error output are generated for a working launch.

I would be happy to make some of these changes if this approach is agreeable to the maintainers. My approach would be to look for the specific standard conditions in the exception handling and eliminate the exception stack trace where present in these cases.
h4. Activity
 * [ Add comment|https://issues.apache.org/jira/secure/AddComment!default.jspa?id=13280451]
h4. People
Assignee:!https://issues.apache.org/jira/secure/useravatar?size=small&avatarId=10453! UnassignedReporter:!https://issues.apache.org/jira/secure/useravatar?size=small&avatarId=10452! Jason Kania
Votes:[0 |https://issues.apache.org/jira/secure/ViewVoters!default.jspa?id=13280451] [Vote for this issue|https://issues.apache.org/jira/secure/VoteOrWatchIssue.jspa?atl_token=A5KQ-2QAV-T4JA-FDED_909568095f49e2254ecb8cf832080a6c48df0cfe_lin&id=13280451&vote=vote] Watchers:[1 |https://issues.apache.org/jira/secure/ManageWatchers!default.jspa?id=13280451]
 [Start watching this issue|https://issues.apache.org/jira/secure/VoteOrWatchIssue.jspa?atl_token=A5KQ-2QAV-T4JA-FDED_909568095f49e2254ecb8cf832080a6c48df0cfe_lin&id=13280451&watch=watch] 
h4. Dates
Created:20/Jan/20 01:27Updated:20/Jan/20 01:29
{panel}
h4. Agile
{panel}
h4. Slack
22 of 230
Previous Issue'ZOOKEEPER-3814'
Next Issue'ZOOKEEPER-3607'stop all stack overflow apply apache flex. Control apachecommand and apachehttpjavaclient

> GSoC 2022 Idea: Instant Instance Deploy (using VM Definitions)
> --------------------------------------------------------------
>
>                 Key: CLOUDSTACK-10451
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10451
>             Project: CloudStack
>          Issue Type: Improvement
>      Security Level: Public(Anyone can view this level - this is the default.) 
>            Reporter: Suresh Kumar Anaparti
>            Priority: Major
>              Labels: gsoc2022, mentor
>   Original Estimate: 175h
>  Remaining Estimate: 175h
>
> h2. Background
> Currently, Deploy Instances/Virtual Machines(VMs) in Cloudstack requires to specify some offerings, template and other settings through the API (check the API here: [https://cloudstack.apache.org/api/apidocs-4.16/apis/deployVirtualMachine.html]) or the 'Instance Deployment Wizard' in the UI.
> h2. Requirement
> Provision to user/operator to quick deploy an instance using a VM definition/profile. The VM definition/profile would hold the details of the template, offerings (including any custom values - size, iops), ssh keypair, instance group, affinity group and other settings (boot type, dynamic scaling, userdata, keyboard language, etc) that are required, and the underlying definition/profile id can be used to launch an instance. At the minimum, the definition should hold all the mandatory details for deploying an instance. With this, only the VM definitions/profiles (and other important options, with the associated billing details) can be exposed to the users for VM deployment, instead of the offerings and other VM options.
> Need to add new APIs (and/or UI) support for the VM definition/profile CRUD operations, and support for definition in the deployVirtualMachine API.
> h2. Relevant Skills
>  * Java, MySQL
>  * Vue.js (for UI)
>  * Some knowledge of Virtualization and CloudStack
> h2. Difficulty
> Medium
> h2. Potential Mentors
>  * Suresh Kumar Anaparti
>  * David Jumani
> h2. Project Scope/Duration
> Medium / 175 hours
> h2. References
>  * [http://docs.cloudstack.apache.org/en/latest/adminguide/index.html#working-with-virtual-machines]
>  * [https://cloudstack.apache.org/api/apidocs-4.16/apis/deployVirtualMachine.html]
>  * [https://cloudstack.apache.org/api/apidocs-4.16/]



--
This message was sent by Atlassian Jira
(v8.20.1#820001)