This is an automated email from the ASF dual-hosted git repository.
pearl11594 pushed a change to branch main-update
in repository https://gitbox.apache.org/repos/asf/cloudstack.git
discard 7120f803997 Merge 4.20 into main
omit 1c2c7e3de67 Phase4 - Add support for Source NAT, Static NAT and Port
Forwarding (#19)
omit 2ae0703ae52 Add support to create Netris VPC / Network offerings (#22)
omit c02592e2810 Run moodifyvxlan script if broadcast domain type is Netris
(#18)
omit 04f11827730 Pass network gateway instead of network CIDR for Netris
vNet creation (#21)
omit f1f3450700a Fix VR Public IP address (#20)
omit 518d010906f Update Subnet purpose for Netris Public Traffic (#17)
omit b038bc6a65f Pass VXLAN ID during creation of Netris vNets (#16)
omit 5d7f0649c7e Set up Netris Public range on new zone addition (#15)
omit 2d561b3605e Add missing suffix return (#14)
omit 773870ad47b Add support to delete VNets and Subnets (#13)
omit 294fa064e96 Fix unit tests
omit 76c2e782a19 Support adding netris provider to CloudStack and Netris
VPC Creation (#6)
omit c3d7e8195bf Delegate API classes creation to the SDK and simply invoke
the desired API class through CloudStack (#7)
omit 36f75ce3ef1 List tenants
omit 54edfb2ef79 Support for listing VPCs (#5)
omit 4e5a79b87ad Add dependency and Netris API client (#4)
omit 6b7f32b0a92 fix failing build
omit 0cd6c01259c Add routed mode offerings for Netris VPC (#3)
omit 50a29798fc7 Add missing config key
omit b7d3be65cc0 cleanup
omit f41e3899b27 add steps to zone wizard for adding netris controller and
public traffic
omit 5ef984c6039 Add Netris Provider to the zone creation wizard
omit d5cdc62e91c Fix
omit 5ebd693acfb Add Netris module and Add netris provider
add e8ac477e9f8 engine/orchestration: fix missing vm powerstate update vm
state (#10407)
add 37c4df9ada1 fix: enforce the cpu shares within allowed range (#10221)
new c349a2e3d96 Merge 4.20 into main
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (7120f803997)
\
N -- N -- N refs/heads/main-update (c349a2e3d96)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
