I have used the Eucalyptus faststart ISO (3.4.2) to set up a frontend controller and 5 node controllers. The problem that I am having is that the faststart ISO installation of the frontend system only allows you to enter 5 ip addresses for node controllers. I have 4 more machines that I want to be node controllers but when I try to register them I get this screen when I run the euca-describe-services --all command. Note the additional nodes showing up as "DISABLED".
[root#frontend1 sbin]# euca-describe-services --all
SERVICE loadbalancing loadbalancing 10.162.12.1 ENABLED 40 http://10.162.12.1:8773/services/LoadBalancing arn:euca:eucalyptus:loadbalancing:loadbalancing:10.162.12.1/
SERVICE reporting bootstrap 10.162.12.1 ENABLED 40 http://10.162.12.1:8773/services/Reporting arn:euca:bootstrap::reporting:10.162.12.1/
SERVICE dns eucalyptus 10.162.12.1 ENABLED 40 http://10.162.12.1:8773/services/Dns arn:euca:eucalyptus::dns:10.162.12.1/
SERVICE component bootstrap 10.162.12.1 ENABLED 40 http://10.162.12.1:8773/services/Component arn:euca:bootstrap::component:10.162.12.1/
SERVICE cloudwatch cloudwatch 10.162.12.1 ENABLED 40 http://10.162.12.1:8773/services/CloudWatch arn:euca:eucalyptus:cloudwatch:cloudwatch:10.162.12.1/
SERVICE autoscaling autoscaling 10.162.12.1 ENABLED 40 http://10.162.12.1:8773/services/AutoScaling arn:euca:eucalyptus:autoscaling:autoscaling:10.162.12.1/
SERVICE notifications eucalyptus 10.162.12.1 ENABLED 40 http://10.162.12.1:8773/services/Notifications arn:euca:eucalyptus::notifications:10.162.12.1/
SERVICE jetty eucalyptus 10.162.12.1 ENABLED 40 http://10.162.12.1:8773/services/Jetty arn:euca:eucalyptus::jetty:10.162.12.1/
SERVICE db eucalyptus 10.162.12.1 ENABLED 40 postgresql://10.162.12.1:8777/eucalyptus?ssl=true&sslfactory=com.eucalyptus.postgresql.PostgreSQLSSLSocketFactory arn:euca:eucalyptus::db:10.162.12.1/
SERVICE configuration eucalyptus 10.162.12.1 ENABLED 40 http://10.162.12.1:8773/services/Configuration arn:euca:eucalyptus::configuration:10.162.12.1/
SERVICE eucalyptus eucalyptus 10.162.12.1 ENABLED 40 http://10.162.12.1:8773/services/Eucalyptus arn:euca:eucalyptus:::10.162.12.1/
SERVICE bootstrap bootstrap 10.162.12.1 ENABLED 40 http://10.162.12.1:8773/services/Empyrean arn:euca:bootstrap:::10.162.12.1/
SERVICE ldap eucalyptus 10.162.12.1 ENABLED 40 http://10.162.12.1:8773/services/Ldap arn:euca:eucalyptus::ldap:10.162.12.1/
SERVICE tokens eucalyptus 10.162.12.1 ENABLED 40 http://10.162.12.1:8773/services/Tokens arn:euca:eucalyptus::tokens:10.162.12.1/
SERVICE properties bootstrap 10.162.12.1 ENABLED 40 http://10.162.12.1:8773/services/Properties arn:euca:bootstrap::properties:10.162.12.1/
SERVICE node CLUSTER01 10.162.12.10 DISABLED 40 http://10.162.12.10:8775/axis2/services/EucalyptusNC arn:euca:bootstrap:CLUSTER01:node:10.162.12.10/
SERVICE node CLUSTER01 10.162.12.2 ENABLED 40 http://10.162.12.2:8775/axis2/services/EucalyptusNC arn:euca:bootstrap:CLUSTER01:node:10.162.12.2/
SERVICE node CLUSTER01 10.162.12.3 ENABLED 40 http://10.162.12.3:8775/axis2/services/EucalyptusNC arn:euca:bootstrap:CLUSTER01:node:10.162.12.3/
SERVICE node CLUSTER01 10.162.12.4 ENABLED 40 http://10.162.12.4:8775/axis2/services/EucalyptusNC arn:euca:bootstrap:CLUSTER01:node:10.162.12.4/
SERVICE node CLUSTER01 10.162.12.5 ENABLED 40 http://10.162.12.5:8775/axis2/services/EucalyptusNC arn:euca:bootstrap:CLUSTER01:node:10.162.12.5/
SERVICE node CLUSTER01 10.162.12.7 DISABLED 40 http://10.162.12.7:8775/axis2/services/EucalyptusNC arn:euca:bootstrap:CLUSTER01:node:10.162.12.7/
SERVICE node CLUSTER01 10.162.12.8 DISABLED 40 http://10.162.12.8:8775/axis2/services/EucalyptusNC arn:euca:bootstrap:CLUSTER01:node:10.162.12.8/
SERVICE node CLUSTER01 10.162.12.9 DISABLED 40 http://10.162.12.9:8775/axis2/services/EucalyptusNC arn:euca:bootstrap:CLUSTER01:node:10.162.12.9/
SERVICE storage CLUSTER01 sc_01 ENABLED 40 http://10.162.12.1:8773/services/Storage arn:euca:eucalyptus:CLUSTER01:storage:sc_01/
SERVICE walrus walrus walrus ENABLED 40 http://10.162.12.1:8773/services/Walrus arn:euca:bootstrap:walrus:walrus:walrus/
SERVICE imaging imaging 10.162.12.1 ENABLED 40 http://10.162.12.1:8773/services/Imaging arn:euca:bootstrap:imaging:imaging:10.162.12.1/
SERVICE cluster CLUSTER01 cc_01 ENABLED 40 http://10.162.12.1:8774/axis2/services/EucalyptusCC arn:euca:eucalyptus:CLUSTER01:cluster:cc_01/
SERVICE euare eucalyptus 10.162.12.1 ENABLED 40 http://10.162.12.1:8773/services/Euare arn:euca:eucalyptus::euare:10.162.12.1/
Faststart is not intended for use with larger installations:
Eucalyptus Faststart is intended for smaller deployments. For larger
Eucalyptus deployments that require separation of components, see
Eucalyptus Installation or Eucalyptus HA Installation.
From:
https://www.eucalyptus.com/docs/eucalyptus/3.4/index.html#install-guide/faststart.html
You need to follow the regular installation documentation:
https://www.eucalyptus.com/docs/eucalyptus/3.4/index.html#install-guide/eucalyptus.html
Related
I noticed that in Devstack (deloyment with default configuration from the quickstart guide), Neutron is the only one API not exposed within HTTPD using a WSGI frontend.
So, in the OpenStack catalog, the referenced URL is the one directly exposed by neutron-server.
What is the reason behind that ? Is there a way in Devstack to enable it ?
I found configuration flags in the Devstack documentation to enable/disable WSGI for other OpenStack services but nothing about Neutron.
I'm using 2 instances of WSO2 API Manager 2.1.0 within the same node. (one instance as a gateway which is exposed to DMZ)
I tried to configure the WSO2 Analytics Server and came up with the following concern.
Since the gateway is already up and running with an offset of 1, how should I be setting the offset in the Analytics Server in order to get it to work? In the documentation, I noticed this: "By default, WSO2 API Manager has a port offset of 0 (no port offset) and WSO2 API Manager Analytics has an offset of 1. Therefore, this guide assumes that you do not have any other carbon servers running on the same machine with port offsets of 0 or 1." If so how should I proceed with configuring the Analytics Server?
Should I configure 2 Analytics Servers for both instances?
Any guidance for these concerns is highly appreciated.
Thanks in advance.
Configure a different port offset for the analytics server. You can configure the offset in <ANALYTICS_HOME>/repository/conf/carbon.xml. Set the offset as <Offset>2</Offset>. By configuring this, Your analytics server can be up in a different port (APIM_PORT+2).
Only one instance of Analytics is enough. Point all your APIM instances to the analytics server you configured.
I have 3 services. One service is for wso2 database. I am using wso2 pattern 2 (active-active all in one) so I have wso2-am 2.6.0 and wso2-am-analytics 2.6.0 in both remained services. I want these two services work active-active.
I configure my services according to this .in part2 configure load balancer: I don't want to use NGINX and I want to use IIS. I try to config IIS in my local according to this . So I define two services (IP of my services) in service frim of IIS. I am not sure that I config right and I don't know how test it. how host names of wso2 set in IIS?
Is it possible to use IIS instead of NGINX for load balance support in wso2?
I am trying to add DataPower 7.7 into API Management 2018.1.
I need to configure API Connect Gateway Service in DataPower (new APIC 2018.1 doesn't work with XML Management Service).
After configuration I got an error:
8:07:19 mgmt notice 959 0x00350015 apic-gw-service (default):
Operational state down
8:07:19 apic-gw-service error 959 0x88e00001 apic-gw-service
(default): Unexpected queue error: Domain check failed! Please ensure that
the 'default' domain exists and is enabled. Also, please verify that the API
Gateway Service is configured with the correct domain and SOMA credentials.
8:07:19 apic-gw-service error 959 0x88e000a0 apic-gw-service
(default): Failed to initialize gateway environment: datapower
DP version is 7.7.
Please suggest, if you have any information or manuals.
Note: Domain exists, main services are enabled
It's hard to tell what exactly the problem is based on the log messages shown above.
Update to original answer:
See also the documentation that is now available in the IBM API Connect Knowledge Center: https://www.ibm.com/support/knowledgecenter/SSMNED_2018/com.ibm.apic.install.doc/tapic_install_datapower_gateway.html
However, here are the basic steps for configuring a DataPower gateway to work with API Connect 2018.x.
You will need to ensure:
DataPower is running DP 7.7.0.0 or higher.
You have the AppOpt license installed. (Use the “show license” command in the DataPower CLI to confirm.)
You have a shared certificate and a private key for securing the
communication between the API Connect management server and the
gateway.
On DataPower, you need to:
Create an application domain. All of the subsequent configuration should be done in the application domain.
Enable statistics
Upload your private key and shared certificate to the cert:// directory in the application domain.
Create a crypto key object, a crypto certificate and a crypto identification credentials object using your key and certificate.
Create an SSL client profile and an SSL server profile that reference the crypto identification credential object.
Configure a gateway-peering object.
Configure and enable the API Connect Gateway Service in the application domain.
At that point, you should be able to configure the gateway in the API Connect cloud manager.
Here are the DataPower CLI commands to create a basic configuration. In the configuration below, IP address 1.1.1.1 represents a local IP address on your DataPower appliance. Traffic from the API Connect management server to the gateway will be sent to port 3000. API requests will go to port 9443 (but you can change it to the more standard port, 443, if you prefer.)
For a production environment, you will want to build on this configuration to ensure you are running with at least 3 gateways in the peer group, but this will get you started.
Create the application domain called apiconnect
top; configure terminal;
domain apiconnect; visible default; exit;
write mem
Use the Web GUI to upload your private key and shared certificate to the cert:// folder in the apiconnect domain
Then run these commands to create the configuration in the apiconnect domain
switch apiconnect
statistics
crypto
key gw_to_apic cert:///your-privkey.cer
certificate gw_to_apic cert:///your-sscert.cer
idcred gw_to_apic gw_to_apic gw_to_apic
ssl-client gwd_to_mgmt
idcred gw_to_apic
no validate-server-cert
exit
ssl-server gwd_to_mgmt
idcred gw_to_apic
no request-client-auth
validate-client-cert off
exit
exit
gateway-peering apic
admin-state enabled
local-address 1.1.1.1
local-port 15379
monitor-port 25379
priority 100
enable-ssl off
enable-peer-group off
persistence local
exit
apic-gw-service
admin-state enabled
local-address 0.0.0.0
local-port 3000
api-gw-address 0.0.0.0
api-gw-port 9443
v5-compatibility-mode on
gateway-peering apic
ssl-server gwd_to_mgmt
ssl-client gwd_to_mgmt
exit
write mem
The problem you are seeing is an issue with creating your api connect service in the default domain. To work around just put your Api Gateway Service in a domain other than default.
If gateway server is installed in one server and api manager installed in another server and I have configured DAS in api manager server. Will my DAS server can collect statistics data from api manager server?
If you are using gateway manager or gateway worker profile then you need to enable below OSGI bundles in bundles.info for that profile
org.wso2.carbon.bam.service.data.publisher.stub,4.6.0,../plugins/org.wso2.carbon.bam.service.data.publisher.stub_4.6.0.jar,4,true
org.wso2.carbon.bam.service.data.publisher.ui,4.6.0,../plugins/org.wso2.carbon.bam.service.data.publisher.ui_4.6.0.jar,4,true
org.wso2.carbon.statistics,4.4.8,../plugins/org.wso2.carbon.statistics_4.4.8.jar,4,true
org.wso2.carbon.statistics.stub,4.4.8,../plugins/org.wso2.carbon.statistics.stub_4.4.8.jar,4,true
org.wso2.carbon.statistics.ui,4.4.8,../plugins/org.wso2.carbon.statistics.ui_4.4.8.jar,4,true