[jira] [Closed] (CLOUDSTACK-10441) CloudStack GSoC 2022 Ideas
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boris Stoyanov closed CLOUDSTACK-10441. --- Resolution: Won't Fix > CloudStack GSoC 2022 Ideas > -- > > Key: CLOUDSTACK-10441 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10441 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Boris Stoyanov >Priority: Major > Labels: gsoc2022, mentor > > Hello Students! We are the Apache CloudStack project. From our [project > website|http://cloudstack.apache.org/]: "Apache CloudStack is open source > software designed to deploy and manage large networks of virtual machines, as > a highly available, highly scalable Infrastructure as a Service (IaaS) cloud > computing platform. CloudStack is used by a number of service providers to > offer public cloud services, and by many companies to provide an on-premises > (private) cloud offering, or as part of a hybrid cloud solution." > 2-min video on the Apache CloudStack project - > [https://www.youtube.com/watch?v=oJ4b8HFmFTc] > Here's about an hour-long intro to what is CloudStack - > [https://www.youtube.com/watch?v=4qFFwyK9hos] > The general skills student would need are - Java, Python, JavaScript/Vue. > Idea-specific requirements are mentioned on the idea issue. We're a diverse > and welcoming community and we encourage interested students to join the dev > ML: [http://cloudstack.apache.org/mailing-lists.html] > ([d...@cloudstack.apache.org|mailto:d...@cloudstack.apache.org]) > *All our Apache CloudStack GSoC2022 ideas are tracked on the project's Github > issue:* > [https://github.com/apache/cloudstack/issues?q=is%3Aissue+is%3Aopen+label%3Agsoc2022] > > > ||Feature||Skills Required||Difficulty||Potential Mentor||Details and > discussion|| > |List TBD| | | | | -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (CLOUDSTACK-10441) CloudStack GSoC 2022 Ideas
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17499413#comment-17499413 ] Boris Stoyanov commented on CLOUDSTACK-10441: - Closing this one as it does not make much sense > CloudStack GSoC 2022 Ideas > -- > > Key: CLOUDSTACK-10441 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10441 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Boris Stoyanov >Priority: Major > Labels: gsoc2022, mentor > > Hello Students! We are the Apache CloudStack project. From our [project > website|http://cloudstack.apache.org/]: "Apache CloudStack is open source > software designed to deploy and manage large networks of virtual machines, as > a highly available, highly scalable Infrastructure as a Service (IaaS) cloud > computing platform. CloudStack is used by a number of service providers to > offer public cloud services, and by many companies to provide an on-premises > (private) cloud offering, or as part of a hybrid cloud solution." > 2-min video on the Apache CloudStack project - > [https://www.youtube.com/watch?v=oJ4b8HFmFTc] > Here's about an hour-long intro to what is CloudStack - > [https://www.youtube.com/watch?v=4qFFwyK9hos] > The general skills student would need are - Java, Python, JavaScript/Vue. > Idea-specific requirements are mentioned on the idea issue. We're a diverse > and welcoming community and we encourage interested students to join the dev > ML: [http://cloudstack.apache.org/mailing-lists.html] > ([d...@cloudstack.apache.org|mailto:d...@cloudstack.apache.org]) > *All our Apache CloudStack GSoC2022 ideas are tracked on the project's Github > issue:* > [https://github.com/apache/cloudstack/issues?q=is%3Aissue+is%3Aopen+label%3Agsoc2022] > > > ||Feature||Skills Required||Difficulty||Potential Mentor||Details and > discussion|| > |List TBD| | | | | -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (CLOUDSTACK-10431) Mapping existing configuration parameters to the APIs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17499441#comment-17499441 ] Boris Stoyanov commented on CLOUDSTACK-10431: - OK [~harikrishna.patnala], please remove the label so it don't end up in results. Thanks. > Mapping existing configuration parameters to the APIs > - > > Key: CLOUDSTACK-10431 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10431 > Project: CloudStack > Issue Type: Improvement > Components: API, Management Server >Reporter: Harikrishna Patnala >Priority: Major > Labels: gsoc2021, mentor > > Hello students, > The following improvement will be a good addition to CloudStack and helps you > learning a good product on a broad view. > Background: > Cloudstack has global settings in which there are around 672 configuration > parameters. Using these parameters one can adjust the values according to the > need of the environment. For example "allow.duplicate.networkname" default > value of this parameter is true, which means networks can be created with > same name in an account. If the value is set to false then duplicate network > names are not allowed. > Problem statement: > When admin wants to change the API behaviour or during debugging an issue, > admin has to search for the corresponding configuration parameter. The only > way currently everyone is using is by using string search or looking into > corresponding documentation. Searching over 672 configuration parameters > which is a huge list is not straight forward or may lead to missing few > parameters. > > Solution: > To address this problem I would like to propose the solution which maps the > configurations parameters to the corresponding APIs. One can know what are > the configuration parameters involved for a specific API. For example > "createNetwork" API will be mapped to "allow.duplicate.networkname". When > admin wants to see what are the configuration parameters used for > "createNetwork" API , this mapping will help. In the final result we will > have a table with APIs in one column and configuration parameters in another > column. > Skills Required: > * Java > * Python > More details at https://github.com/apache/cloudstack/issues/4825 > Good luck. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (CLOUDSTACK-10431) Mapping existing configuration parameters to the APIs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harikrishna Patnala updated CLOUDSTACK-10431: - Labels: (was: gsoc2021 mentor) > Mapping existing configuration parameters to the APIs > - > > Key: CLOUDSTACK-10431 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10431 > Project: CloudStack > Issue Type: Improvement > Components: API, Management Server >Reporter: Harikrishna Patnala >Priority: Major > > Hello students, > The following improvement will be a good addition to CloudStack and helps you > learning a good product on a broad view. > Background: > Cloudstack has global settings in which there are around 672 configuration > parameters. Using these parameters one can adjust the values according to the > need of the environment. For example "allow.duplicate.networkname" default > value of this parameter is true, which means networks can be created with > same name in an account. If the value is set to false then duplicate network > names are not allowed. > Problem statement: > When admin wants to change the API behaviour or during debugging an issue, > admin has to search for the corresponding configuration parameter. The only > way currently everyone is using is by using string search or looking into > corresponding documentation. Searching over 672 configuration parameters > which is a huge list is not straight forward or may lead to missing few > parameters. > > Solution: > To address this problem I would like to propose the solution which maps the > configurations parameters to the corresponding APIs. One can know what are > the configuration parameters involved for a specific API. For example > "createNetwork" API will be mapped to "allow.duplicate.networkname". When > admin wants to see what are the configuration parameters used for > "createNetwork" API , this mapping will help. In the final result we will > have a table with APIs in one column and configuration parameters in another > column. > Skills Required: > * Java > * Python > More details at https://github.com/apache/cloudstack/issues/4825 > Good luck. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (CLOUDSTACK-10453) GSoC 2022 Idea: CloudStack Edge Zones
Pearl Dsilva created CLOUDSTACK-10453: - Summary: GSoC 2022 Idea: CloudStack Edge Zones Key: CLOUDSTACK-10453 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10453 Project: CloudStack Issue Type: New Feature Security Level: Public (Anyone can view this level - this is the default.) Reporter: Pearl Dsilva ## Background Over recent years, Edge computing has been gaining popularity as it defines a model that brings compute and storage closer to where they are consumed by the end-user. By being closer to the end-user a better experience can be provided with reduction on overall latency, lower bandwidth requirements, lower TCO, more flexible hardware/software model, while also ensuring security and reliability. To align ACS with this evolving cloud computing model we would like to propose an idea of supporting Edge Zones in CloudStack, which can be also looked upon as a lightweight zone, with minimal resources. ## Requirement Today, when a Zone is setup in CloudStack, it by default comes up with a secondary storage VM(SSVM) and a console proxy VM(CPVM). As part of this project, we would need to define a new zone type to decide the change in workflow required to ensure that a CPVM & SSVM isn't spawned up by default. Basic characteristics of an Edge zone include: - no need for Secondary Storage - no Secondary Storage VM - no Console Proxy VM - Local storage only as typically an edge device comprises of a single compute node (host) - And supports L2 and Isolated networks. A high-level view of an edge zone would look something like:  ## Relevant Skills: Java MySQL Vue.js (Basic) ## Difficulty Medium ## Project Duration: 175 hours ## Potential Mentors Alex Mattioli Nicolas Vazquez Pearl Dsilva -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (CLOUDSTACK-10453) GSoC 2022 Idea: CloudStack Edge Zones
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pearl Dsilva updated CLOUDSTACK-10453: -- Attachment: image-2022-03-01-17-30-52-329.png > GSoC 2022 Idea: CloudStack Edge Zones > - > > Key: CLOUDSTACK-10453 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10453 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Pearl Dsilva >Priority: Major > Labels: cloudstack, gsoc2022 > Attachments: image-2022-03-01-17-30-30-509.png, > image-2022-03-01-17-30-52-329.png > > > ## Background > Over recent years, Edge computing has been gaining popularity as it defines a > model that brings compute and storage closer to > where they are consumed by the end-user. By being closer to the end-user a > better experience can be provided with reduction on overall latency, lower > bandwidth requirements, lower TCO, more flexible hardware/software model, > while also ensuring security and reliability. To align ACS with this evolving > cloud computing model we would like to propose an idea of supporting Edge > Zones in CloudStack, which > can be also looked upon as a lightweight zone, with minimal resources. > ## Requirement > Today, when a Zone is setup in CloudStack, it by default comes up with a > secondary storage VM(SSVM) and a console proxy VM(CPVM). As part of this > project, we would need to define a new zone type to decide the change in > workflow required to ensure that a CPVM & SSVM isn't spawned up by default. > Basic characteristics of an Edge zone include: > - no need for Secondary Storage > - no Secondary Storage VM > - no Console Proxy VM > - Local storage only as typically an edge device comprises of a single > compute node (host) > - And supports L2 and Isolated networks. > A high-level view of an edge zone would look something like: >  > ## Relevant Skills: > Java > MySQL > Vue.js (Basic) > ## Difficulty > Medium > ## Project Duration: > 175 hours > ## Potential Mentors > Alex Mattioli > Nicolas Vazquez > Pearl Dsilva > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (CLOUDSTACK-10453) GSoC 2022 Idea: CloudStack Edge Zones
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pearl Dsilva updated CLOUDSTACK-10453: -- Attachment: image-2022-03-01-17-30-30-509.png > GSoC 2022 Idea: CloudStack Edge Zones > - > > Key: CLOUDSTACK-10453 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10453 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Pearl Dsilva >Priority: Major > Labels: cloudstack, gsoc2022 > Attachments: image-2022-03-01-17-30-30-509.png, > image-2022-03-01-17-30-52-329.png > > > ## Background > Over recent years, Edge computing has been gaining popularity as it defines a > model that brings compute and storage closer to > where they are consumed by the end-user. By being closer to the end-user a > better experience can be provided with reduction on overall latency, lower > bandwidth requirements, lower TCO, more flexible hardware/software model, > while also ensuring security and reliability. To align ACS with this evolving > cloud computing model we would like to propose an idea of supporting Edge > Zones in CloudStack, which > can be also looked upon as a lightweight zone, with minimal resources. > ## Requirement > Today, when a Zone is setup in CloudStack, it by default comes up with a > secondary storage VM(SSVM) and a console proxy VM(CPVM). As part of this > project, we would need to define a new zone type to decide the change in > workflow required to ensure that a CPVM & SSVM isn't spawned up by default. > Basic characteristics of an Edge zone include: > - no need for Secondary Storage > - no Secondary Storage VM > - no Console Proxy VM > - Local storage only as typically an edge device comprises of a single > compute node (host) > - And supports L2 and Isolated networks. > A high-level view of an edge zone would look something like: >  > ## Relevant Skills: > Java > MySQL > Vue.js (Basic) > ## Difficulty > Medium > ## Project Duration: > 175 hours > ## Potential Mentors > Alex Mattioli > Nicolas Vazquez > Pearl Dsilva > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (CLOUDSTACK-10453) GSoC 2022 Idea: CloudStack Edge Zones
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pearl Dsilva updated CLOUDSTACK-10453: -- Description: h2. *Background* Over recent years, Edge computing has been gaining popularity as it defines a model that brings compute and storage closer to where they are consumed by the end-user. By being closer to the end-user a better experience can be provided with reduction on overall latency, lower bandwidth requirements, lower TCO, more flexible hardware/software model, while also ensuring security and reliability. To align ACS with this evolving cloud computing model we would like to propose an idea of supporting Edge Zones in CloudStack, which can be also looked upon as a lightweight zone, with minimal resources. h2. *Requirement* Today, when a Zone is setup in CloudStack, it by default comes up with a secondary storage VM(SSVM) and a console proxy VM(CPVM). As part of this project, we would need to define a new zone type to decide the change in workflow required to ensure that a CPVM & SSVM isn't spawned up by default. Basic characteristics of an Edge zone include: - no need for Secondary Storage - no Secondary Storage VM - no Console Proxy VM - Local storage only as typically an edge device comprises of a single compute node (host) - And supports L2 and Isolated networks. A high-level view of an edge zone would look something like: !image-2022-03-01-17-30-52-329.png! h2. *Relevant Skills:* Java MySQL Vue.js (Basic) h2. *Difficulty:* Medium h2. *Project Duration:* 175 hours h2. *Potential Mentors:* Alex Mattioli Nicolas Vazquez Pearl Dsilva was: ## Background Over recent years, Edge computing has been gaining popularity as it defines a model that brings compute and storage closer to where they are consumed by the end-user. By being closer to the end-user a better experience can be provided with reduction on overall latency, lower bandwidth requirements, lower TCO, more flexible hardware/software model, while also ensuring security and reliability. To align ACS with this evolving cloud computing model we would like to propose an idea of supporting Edge Zones in CloudStack, which can be also looked upon as a lightweight zone, with minimal resources. ## Requirement Today, when a Zone is setup in CloudStack, it by default comes up with a secondary storage VM(SSVM) and a console proxy VM(CPVM). As part of this project, we would need to define a new zone type to decide the change in workflow required to ensure that a CPVM & SSVM isn't spawned up by default. Basic characteristics of an Edge zone include: - no need for Secondary Storage - no Secondary Storage VM - no Console Proxy VM - Local storage only as typically an edge device comprises of a single compute node (host) - And supports L2 and Isolated networks. A high-level view of an edge zone would look something like:  ## Relevant Skills: Java MySQL Vue.js (Basic) ## Difficulty Medium ## Project Duration: 175 hours ## Potential Mentors Alex Mattioli Nicolas Vazquez Pearl Dsilva > GSoC 2022 Idea: CloudStack Edge Zones > - > > Key: CLOUDSTACK-10453 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10453 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Pearl Dsilva >Priority: Major > Labels: cloudstack, gsoc2022 > Attachments: image-2022-03-01-17-30-30-509.png, > image-2022-03-01-17-30-52-329.png > > > h2. *Background* > Over recent years, Edge computing has been gaining popularity as it defines a > model that brings compute and storage closer to > where they are consumed by the end-user. By being closer to the end-user a > better experience can be provided with reduction on overall latency, lower > bandwidth requirements, lower TCO, more flexible hardware/software model, > while also ensuring security and reliability. To align ACS with this evolving > cloud computing model we would like to propose an idea of supporting Edge > Zones in CloudStack, which > can be also looked upon as a lightweight zone, with minimal resources. > h2. *Requirement* > Today, when a Zone is setup in CloudStack, it by default comes up with a > secondary storage VM(SSVM) and a console proxy VM(CPVM). As part of this > project, we would need to define a new zone type to decide the change in > workflow required to ensure that a CPVM & SSVM isn't spawned up by default. > Basic characteristics of an Edge zone include: > - no need for Secondary Storage > - no Secondary Storage VM > - no Console Proxy VM > - Local storage only as typically
