This is the multi-page printable view of this section. Click here to print.
New Releases
Eucalyptus 5.1 Released
Eucalyptus Cloud 5.1 has been released with important compatibility and functionality fixes and is recommended for all 5.x deployments.
Fixes of note in this release are:
- CloudFormation AWS::IAM::InstanceProfile add InstanceProfileName property
- ELB cannot connect to https listener
- S3 support for multipart copy
- Web services HTTPS (TLS) should use larger ephemeral Diffie-Hellman key size
You can find the full list of resolved issues in the release notes / milestones.
Eucalyptus 5 Released
Eucalyptus Cloud 5 is now available, this major release includes a new Ansible based installer and technical previews for Route53 and SQS (Simple Queue Service)
In addition to the headline features, there are many smaller changes to improve the AWS compatibility and performance of Eucalyptus Cloud.
New in Eucalyptus 5
Some new features in Eucalyptus 5 are:
- Ansible installer
- Auto Scaling instance protection
- CloudFormation support for YAML templates
- EC2 iam instance profile association
- EC2 long resource identifiers
- Route53 service technical preview
- S3 bucket policy support
- SQS service technical preview
Other notable changes in Eucalyptus 5 are:
- Cluster controller now part of main cloud service
- Java runtime updated to version 11
- Reporting service removed
Full details of changes in Eucalyptus 5 are available in the Corymbia github project and milestone
Try Eucalyptus 5
You can try Eucalyptus 5 with a FastStart install by running:
> bash <(curl -Ls https://get.eucalyptus.cloud)
as root, on a CentOS/RHEL 7.9 minimal install with a few IP addresses to spare.
Miss Eucalyptus 4.4.x?
Eucalyptus 5 look a little different from 4.4.x due to changes with instance types and long identifiers. If you want to try Eucalyptus 5 but with a 4.4.x feel, you can make changes as follows.
To disable EC2 long identifiers, run the following as an administrator:
> euctl cloud.short_identifier_prefixes='*'
changing this setting will cause any new resources to be created with short identifiers (where supported). You can have a mix of short and long identifiers depending on settings when those resources were created.
To change instance types to be the same as 4.4.x, run the following as an administrator:
> euform-create-stack \
--template-file /usr/share/eucalyptus/doc/ec2-instance-types-eucalyptus-4.yaml \
eucalyptus-4-instance-types
> euctl cloud.vmtypes.default_type_name=m1.medium
> euctl services.imaging.worker.instance_type=m1.medium
> euctl services.loadbalancing.worker.instance_type=m1.medium
this will enable 4.4.x instance types and disable the default Eucalyptus 5 instance types. The default instance type and the types used for services are updated accordingly.
Moving to Eucalyptus 5?
Upgrading from previous releases to Eucalyptus 5 is not supported. If moving to Eucalyptus 5 data such as S3 objects and EBS volumes can be copied from existing deployments before they are retired.
Thanks!
Thanks for giving Eucalyptus 5 a try and please use github issues to report any problems you encounter to help improve Eucalyptus.
Eucalyptus 4.4.6 Released
Eucalyptus Cloud 4.4.6 has been released, updating our OS support to allow use of CentOS and RHEL 7.9 in addition to the existing support for 7.x.
This release has some important compatibility and functionality fixes and is recommended for all 4.4.x deployments.
As with version 4.4.5, this release was tested using 2.9.0 qemu packages which should be installed when upgrading from earlier versions.
Some fixes of note in this release are:
- EC2 instance metadata v2 support
- EC2 node controller crash when running windows instance
You can find the full list of resolved issues in the release notes.
If upgrading from 4.4.2 or earlier, note that the RPM repository location has changed, updated Eucalyptus and Euca2ools release RPMs should be installed as detailed in the install guide so that the new downloads.eucalyptus.cloud location is used.
Eucalyptus 5 beta 1 Released
Eucalyptus Cloud 5 beta 1 has been released, this release provides early access for trying out new functionality on non-production deployments.
We are exited to make 5.0 available as a preview to a wider audience to get feedback on new features in advance of the final release of Eucalyptus Cloud 5.
New in Eucalyptus 5
Some new features in Eucalyptus 5 are:
- Auto Scaling instance protection
- CloudFormation support for YAML templates
- EC2 iam instance profile association
- EC2 long resource identifiers
- S3 bucket policy support
- SQS service technical preview
Other notable changes in Eucalyptus 5 are:
- Cluster controller now part of main cloud service
- Java runtime updated to version 11
- Reporting service removed
Full details of changes in Eucalyptus 5 are available in the Corymbia github project
Try Eucalyptus 5
You can try Eucalyptus 5 with a FastStart install by running:
> bash <(curl -Ls https://eucalyptus.cloud/install5ea)
as root, on a CentOS 7.6 minimal install with a few IP addresses to spare.
Miss Eucalyptus 4.4.x?
Eucalyptus 5 look a little different from 4.4.x due to changes with instance types and long identifiers. If you want to try Eucalyptus 5 but with a 4.4.x feel, you can make changes as follows.
To disable EC2 long identifiers, run the following as an administrator:
> euctl cloud.short_identifier_prefixes='*'
changing this setting will cause any new resources to be created with short identifiers (where supported). You can have a mix of short and long identifiers depending on settings when those resources were created.
To change instance types to be the same as 4.4.x, run the following as an administrator:
> euform-create-stack \
--template-file /usr/share/eucalyptus/doc/ec2-instance-types-eucalyptus-4.yaml \
eucalyptus-4-instance-types
> euctl cloud.vmtypes.default_type_name=m1.medium
> euctl services.imaging.worker.instance_type=m1.medium
> euctl services.loadbalancing.worker.instance_type=m1.medium
this will enable 4.4.x instance types and disable the default Eucalyptus 5 instance types. The default instance type and the types used for services are updated accordingly.
Thanks!
Thanks for giving Eucalyptus 5 a try and please use github issues to report any problems you encounter to help improve the final release of Eucalyptus 5.
Eucalyptus 4.4.5 Released
Eucalyptus Cloud 4.4.5 has been released, updating our OS support to allow use of CentOS and RHEL 7.6 in addition to the existing support for 7.3, 7.4, and 7.5.
This release has some important compatibility and functionality fixes and is recommended for all 4.4.x deployments.
As with version 4.4.4, this release was tested using 2.9.0 qemu packages which should be installed when upgrading from earlier versions.
Some fixes of note in this release are:
- The object storage gateway now supports version two object listing
- EC2 instances for some images could hang when starting
You can find the full list of resolved issues in the release notes.
If upgrading from 4.4.2 or earlier, note that the RPM repository location has changed, updated Eucalyptus and Euca2ools release RPMs should be installed as detailed in the install guide so that the new downloads.eucalyptus.cloud location is used.
Eucalyptus 4.4.4 Released
Eucalyptus Cloud 4.4.4 has been released, updating our OS support to allow use of CentOS and RHEL 7.5 in addition to the existing support for 7.3 and 7.4.
This release was tested using updated qemu packages which should be installed when upgrading. This updates qemu to 2.9.0 from the 2.6.0 version previously distributed.
Some fixes of note in this release are:
- The object storage gateway is updated to use less resources for background maintenance when there are buckets with many objects
- The node controller would sometimes leave artifacts behind for terminated instances causing unnecessary disk use
You can find the full list of resolved issues in the release notes.
If upgrading from 4.4.2 or earlier, note that the RPM repository location has changed, updated Eucalyptus and Euca2ools release RPMs should be installed as detailed in the install guide so that the new downloads.eucalyptus.cloud location is used.
Eucalyptus 4.4.3 Released
We are excited to announce the Eucalyptus Cloud 4.4.3 release!
There are a couple of changes included that go beyond those in a typical maintenance release.
The release uses a 2-Clause/Simplified BSD license, which replaces the GPL license used by previous releases. Euca2ools and the management console were already BSD licensed, so with this release the licensing is consistent across the major components.
The RPM repository location has changed, updated Eucalyptus and Euca2ools release RPMs should be installed as detailed in the install guide so that the new downloads.eucalyptus.cloud location is used.
You can find the full list of resolved issues in the release notes.
Eucalyptus Previous Releases
We know how much you love Eucalyptus 4.4, but we also recognize that sometimes a cloud is working well on an older version and upgrading can wait.
In this post we take a look at how you can use the new
downloads.eucalyptus.cloud
RPM repositories with older releases, and
where you can find the related documentation.
Documentation for previous releases
The current documentation has release notes that cover previous versions. Other documentation is available for previous releases as follows:
The above guides are available in PDF format only.
Repositories for previous releases
If using a release earlier than 4.4, please keep in mind that these previous releases are no longer supported or maintained. RPMs are available for previous releases at these locations:
Eucalyptus 4.0:
http://downloads.eucalyptus.cloud/software/eucalyptus/4.0/rhel/6/x86_64/
Eucalyptus 4.1:
http://downloads.eucalyptus.cloud/software/eucalyptus/4.1/rhel/6/x86_64/
Eucalyptus 4.2:
http://downloads.eucalyptus.cloud/software/eucalyptus/4.2/rhel/6/x86_64/
Eucalyptus 4.3:
http://downloads.eucalyptus.cloud/software/eucalyptus/4.3/rhel/6/x86_64/
http://downloads.eucalyptus.cloud/software/eucalyptus/4.3/rhel/7/x86_64/
The 4.3 release can be installed on CentOS/RHEL 6 or 7, so pick the location appropriate for the distribution you are using.
Repository Configuration
You would configure YUM to use the above locations. Here’s an example of
a 4.1 Eucalyptus YUM configuration, you’d put this in a
/etc/yum.repos.d/eucalyptus.repo
file:
[eucalyptus]
name=Eucalyptus 4.1
baseurl=http://downloads.eucalyptus.cloud/software/eucalyptus/4.1/rhel/6/x86_64/
gpgkey=https://downloads.eucalyptus.cloud/software/gpg/eucalyptus-release-key.pub
gpgcheck=1
enabled=1
The baseurl
would be one of the locations listed above.
On the first use after configuration, you may be prompted to confirm the GPG key, which would look something like this:
warning: rpmts_HdrFromFdno: Header V3 RSA/SHA1 Signature, key ID c1240596: NOKEY
Retrieving key from https://downloads.eucalyptus.cloud/software/gpg/eucalyptus-release-key.pub
Importing GPG key 0xC1240596:
Userid: "Eucalyptus Systems, Inc. (release key) <security@eucalyptus.com>"
From : https://downloads.eucalyptus.cloud/software/gpg/eucalyptus-release-key.pub
Is this ok [y/N]: y
Accept the key and you’re good to go!
Conclusion
We hope this helps keep your Eucalyptus clouds running, but please consider using the latest software and documentation from https://eucalyptus.cloud/