bug5946: use rabbit.internal.sapsailing.com for eu-west-1 (default region); explore tags elsewhere

com.sap.sse.landscape.aws.common

Bundle-ActivationPolicy: lazy

Export-Package: com.sap.sailing.landscape.common

package com.sap.sailing.landscape.common;

public interface SharedLandscapeConstants {

/**

* If no specific domain name is provided, e.g., when creating a new application replica set, this will be

*/

String DEFAULT_SECURITY_SERVICE_REPLICA_SET_NAME = "security-service";

/**

* This is the region of the load balancer handling the default traffic for {@code *.sapsailing.com}. It is also

* called the "dynamic" load balancer because adding, removing or changing any hostname-based rule in its HTTPS

* for archived events. If such a state is reached, "dynamic" load balancing may potentially be used regardless

* the region.

*/

/**

* The tag value used to identify host images that can be launched in order to run one or more Sailing Analytics

* server processes on it.

import com.sap.sse.landscape.impl.ReleaseRepositoryImpl;

import com.sap.sse.landscape.mongodb.MongoEndpoint;

import com.sap.sse.landscape.mongodb.impl.DatabaseImpl;

import com.sap.sse.landscape.ssh.SSHKeyPair;

import com.sap.sse.landscape.ssh.SshCommandChannel;

assertEquals(200, healthCheckConnection.getResponseCode());

healthCheckConnection.disconnect();

}

}

com.sap.sse.replication.interfaces,

com.sap.sse.operationaltransformation,

org.mongodb.driver-core;bundle-version="4.3.1",

Web-ContextPath: /landscape

Import-Package: org.apache.shiro;version="1.2.2",

org.osgi.framework;version="1.8.0",

import com.sap.sse.landscape.mongodb.MongoProcessInReplicaSet;

import com.sap.sse.landscape.mongodb.MongoReplicaSet;

import com.sap.sse.landscape.mongodb.impl.MongoProcessImpl;

import com.sap.sse.landscape.ssh.SSHKeyPair;

import software.amazon.awssdk.auth.credentials.AwsBasicCredentials;

String MONGO_REPLICA_SET_NAME_AND_PORT_SEPARATOR = ":";

String CENTRAL_REVERSE_PROXY_TAG_NAME = "CentralReverseProxy";

/**

Iterable<MongoEndpoint> getMongoEndpoints(Region region);

Database getDatabase(Region region, String databaseName);

/**

import com.jcraft.jsch.JSch;

import com.jcraft.jsch.JSchException;

import com.jcraft.jsch.KeyPair;

import com.sap.sse.common.Duration;

import com.sap.sse.common.TimePoint;

import com.sap.sse.common.Util;

}

@Override

final RabbitMQEndpoint result;

} else {

}

return result;

}

}

@Override

public <MetricsT extends ApplicationProcessMetrics, ProcessT extends AwsApplicationProcess<ShardingKey, MetricsT, ProcessT>,

HostT extends ApplicationProcessHost<ShardingKey, MetricsT, ProcessT>>

Iterable<HostT> getApplicationProcessHostsByTag(com.sap.sse.landscape.Region region, String tagName,

import com.sap.sse.landscape.InboundReplicationConfiguration;

import com.sap.sse.landscape.OutboundReplicationConfiguration;

import com.sap.sse.landscape.ProcessConfigurationVariable;

import com.sap.sse.landscape.Release;

import com.sap.sse.landscape.UserDataProvider;

import com.sap.sse.landscape.application.ApplicationProcess;

* {@link #getServerName() server name}.</li>

* <li>The {@link #setInboundReplicationConfiguration(InboundReplicationConfiguration) inbound replication}

* {@link InboundReplicationConfiguration#getInboundRabbitMQEndpoint() RabbitMQ endpoint} defaults to the region's

* configuration}. Note that this setting will take effect only if auto-replication is activated for one or more

* replicables (see {@link InboundReplicationConfiguration#getReplicableIds()}).</li>

* <li>The {@link #setOutboundReplicationConfiguration() outbound replication}

/**

* Obtains the default RabbitMQ configuration for the {@code region} specified. If nothing else is specified

* explicitly, application server replica sets launched in the {@code region} shall use this for their replication

*/

/**

* Tells the regions supported. The underlying hyperscaler may have more, but we may not want to run in all.

*/

The script will ensure the login user's ``authorized_keys`` are updated periodically to contain those of the landscape managers, then will install the necessary packages, particularly ``rabbitmq-server`` and, to get real log files under ``/var/log``, the ``syslog-ng`` package. It then enables the ``rabbitmq_management`` plugin, so access to the management UI becomes possible through port ``15672``. The configuration file under ``/etc/rabbitmq/rabbitmq.conf`` is patched such that guest logins are possible also from non-localhost addresses, by adding the ``loopback_users = none`` directive to the config file. It finally (re-)starts the RabbitMQ server to let these config changes take effect.