5 Commits
Author | SHA1 | Message | Date |
---|---|---|---|
|
700f5c0baf | Log loaded config schema snippets | |
|
3c9ce68ef8 | Switch to Mozilla Public License 2.0 (MPL 2.0) | |
|
f5803765bd | Update copyright (year 2020) | |
|
70428fb0d0 |
URL Cleanup
This commit updates URLs to prefer the https protocol. Redirects are not followed to avoid accidentally expanding intentionally shortened URLs (i.e. if using a URL shortener). # HTTP URLs that Could Not Be Fixed These URLs were unable to be fixed. Please review them to see if they can be manually resolved. * http://blog.listincomprehension.com/search/label/procket (200) with 1 occurrences could not be migrated: ([https](https://blog.listincomprehension.com/search/label/procket) result ClosedChannelException). * http://dozzie.jarowit.net/trac/wiki/TOML (200) with 1 occurrences could not be migrated: ([https](https://dozzie.jarowit.net/trac/wiki/TOML) result SSLHandshakeException). * http://dozzie.jarowit.net/trac/wiki/subproc (200) with 1 occurrences could not be migrated: ([https](https://dozzie.jarowit.net/trac/wiki/subproc) result SSLHandshakeException). * http://e2project.org (200) with 1 occurrences could not be migrated: ([https](https://e2project.org) result AnnotatedConnectException). * http://nitrogenproject.com/ (200) with 2 occurrences could not be migrated: ([https](https://nitrogenproject.com/) result ConnectTimeoutException). * http://proper.softlab.ntua.gr (200) with 1 occurrences could not be migrated: ([https](https://proper.softlab.ntua.gr) result SSLHandshakeException). * http://yaws.hyber.org (200) with 1 occurrences could not be migrated: ([https](https://yaws.hyber.org) result AnnotatedConnectException). * http://choven.ca (503) with 1 occurrences could not be migrated: ([https](https://choven.ca) result ConnectTimeoutException). # Fixed URLs ## Fixed But Review Recommended These URLs were fixed, but the https status was not OK. However, the https status was the same as the http request or http redirected to an https URL, so they were migrated. Your review is recommended. * http://fixprotocol.org/ (301) with 1 occurrences migrated to: https://fixtrading.org ([https](https://fixprotocol.org/) result SSLHandshakeException). * http://erldb.org (UnknownHostException) with 1 occurrences migrated to: https://erldb.org ([https](https://erldb.org) result UnknownHostException). * http://~s:~b/~s (UnknownHostException) with 1 occurrences migrated to: https://~s:~b/~s ([https](https://~s:~b/~s) result UnknownHostException). ## Fixed Success These URLs were switched to an https URL with a 2xx status. While the status was successful, your review is still recommended. * http://cloudi.org/ with 27 occurrences migrated to: https://cloudi.org/ ([https](https://cloudi.org/) result 200). * http://erlware.org/ with 1 occurrences migrated to: https://erlware.org/ ([https](https://erlware.org/) result 200). * http://inaka.github.io/cowboy-trails/ with 1 occurrences migrated to: https://inaka.github.io/cowboy-trails/ ([https](https://inaka.github.io/cowboy-trails/) result 200). * http://ninenines.eu with 6 occurrences migrated to: https://ninenines.eu ([https](https://ninenines.eu) result 200). * http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html with 1 occurrences migrated to: https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html ([https](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html) result 200). * http://www.actordb.com/ with 2 occurrences migrated to: https://www.actordb.com/ ([https](https://www.actordb.com/) result 200). * http://www.cs.kent.ac.uk/projects/wrangler/Home.html with 1 occurrences migrated to: https://www.cs.kent.ac.uk/projects/wrangler/Home.html ([https](https://www.cs.kent.ac.uk/projects/wrangler/Home.html) result 200). * http://www.rebar3.org with 1 occurrences migrated to: https://www.rebar3.org ([https](https://www.rebar3.org) result 200). * http://contributor-covenant.org with 1 occurrences migrated to: https://contributor-covenant.org ([https](https://contributor-covenant.org) result 301). * http://contributor-covenant.org/version/1/3/0/ with 1 occurrences migrated to: https://contributor-covenant.org/version/1/3/0/ ([https](https://contributor-covenant.org/version/1/3/0/) result 301). * http://inaka.github.com/apns4erl with 1 occurrences migrated to: https://inaka.github.com/apns4erl ([https](https://inaka.github.com/apns4erl) result 301). * http://inaka.github.com/edis/ with 1 occurrences migrated to: https://inaka.github.com/edis/ ([https](https://inaka.github.com/edis/) result 301). * http://lasp-lang.org/ with 1 occurrences migrated to: https://lasp-lang.org/ ([https](https://lasp-lang.org/) result 301). * http://saleyn.github.com/erlexec with 1 occurrences migrated to: https://saleyn.github.com/erlexec ([https](https://saleyn.github.com/erlexec) result 301). * http://www.mozilla.org/MPL/ with 9 occurrences migrated to: https://www.mozilla.org/MPL/ ([https](https://www.mozilla.org/MPL/) result 301). * http://zhongwencool.github.io/observer_cli with 1 occurrences migrated to: https://zhongwencool.github.io/observer_cli ([https](https://zhongwencool.github.io/observer_cli) result 301). # Ignored These URLs were intentionally ignored. * http://localhost:~w~s/~s with 1 occurrences |
|
|
205a9ac403 |
Initial version of the VM-based test framework
It allows one to run a common_test testsuite on Erlang nodes running on remote Amazon EC2 VMs. It configures Erlang distribution so that remote nodes can communicate with each other and also commmunicate with the commont_test master node. rabbit_ct_broker_helpers also offers new setup and teardown steps to work with VMs: it allows to start RabbitMQ nodes on those VMS and possible cluster them. The configuration is unchanged compared to local nodes. The number of RabbitMQ nodes doesn't have to match the number of VMs: they are spread using round-robin on the available VMs. v2: Add support to start RabbitMQ nodes spread on remote VMs. v3: Various improvements to allow parallel executions of testcases. I.e. several sets of VMs can be spawned in parallel without interference. v4: Support user-specified VM names. If the name is missing, use the unique ID generated for per-VM-set resources. v5: Use a unique local node name when trying to ping the remote ct-peer. While here use `rabbit_misc:random()` to create Terraform unique UI. The previous base64-encoded string didn't make a valid node name. Accept `$ERLANG_VERSION` environment/make variable to force the Erlang version to use on VMs. Add setup scripts for Erlang 19.3 and 20.1. v6: Use Amazon S3 to upload the directories archive. Configure a VPC to access it from the VMs. Use `user_data` to provide the setup script. The setup script itself is now a template. Those changes allow to get rid of all `exec` or `file` provisioners in the `aws_instance`. This means it can now be created using a launch configuration which is the way to create instances via an autoscaling group. v7: Export hostnames, nodenames and IP addresses from Terraform state, and generate `inetrc` in Erlang. This makes it possible to work with a "two-step Terraform manifest". For instance, with an autoscaling group, Terraform doesn't start instances. However, we can use a second manifest to query the created instances. Export `$HOME` in setup scripts. This fixes the use of `~/...` paths and the start of the remote Erlang node. v8: Add support to query Amazon EC2 VMs, based on tags, instead of relying on the outputs of the manifest. This will allow us to query VMs created with an autoscaling group for instance. This change is based on a new query-only manifest called `vms-query`. This new query-only manifest is used in a loop until we have enough VMs (compared to the requested numbers) or we reach a timeout of 5 minutes. v9: Add an autoscaling-group-based module to deploy VMs. The testsuite is extended to use it, in addition to the `direct-vms` module. Fix the setup scripts to handle the case where there is no directories to upload (i.e. the archive is an empty file). v10: Download log files from remote VMs before destroying them. This allows further debugging if something fails. v11: Use a per-VPC CIDR block. This resolves a possible conflict when VMs in different VPCs gets the same private IP address: this breaks name resolution on the local common_test node. Use inet_db:add_host() to reconfigure name resolution, instead of calling inet_config:init(). We still write the `inetrc` files: they are used by sub-processes such as rabbitmqctl(8) and rabbitmq-plugins(8). Download each VM's common_test priv_dir before destroying the VMs. They are useful because they contain the RabbitMQ nodes logs for instance. Fix several concurrency bugs around global resources accessed or shared by several setups of rabbit_vm_helpers, in case of parallel testing. The upload dirs archive is now created by Erlang, not Terraform. It allows us to create a single archive per directories set, which saves time, I/O and CPU (for compression). Configure an EBS root block device for each VM because the default internal storage a `t2.micro` instance type is too small. v12: Verify that terraform(1) is available and working before doing anything else. v13: Guess the Erlang application name being tested (using the value of the `$DIALYZER_PLT` environment variable, lacking a better way). We use it now as the instance name prefix. Allow the caller to set the AWS EC2 region. Allow the caller to set the files suffix. Also, we record it in the instance and launch configuration tags. This allows the caller to do things based on a known instance tag. Install rsync, zip and vim-nox on VMs. They are useful when one needs to connect to the VMs and try things. Install Elixir on 19.3+ VMs. It's not used, but it silences a warnings from `rabbitmq-build.mk` which calls it to initialize `$ELIXIR_LIB_DIR`. [#153749132] |