Ubuntu: How to resolve Err:4 http://security.ubuntu.com/ubuntu cosmic-updates/main amd64 libsnmp-base all 5.7.3+dfsg-1.8ubuntu3.18.10.1 404 Not Found

Ubuntu: How to resolve Err:4 http://security.ubuntu.com/ubuntu cosmic-updates/main amd64 libsnmp-base all 5.7.3+dfsg-1.8ubuntu3.18.10.1   404  Not Found

This happens because you still have somehow the sources.list file for Ubuntu 13.10 on your machine:

You can use sudo -i in terminal and copy & paste the following (complete block) into it:

cat > /etc/apt/sources.list << EOF
deb http://archive.ubuntu.com/ubuntu xenial main restricted universe multiverse
deb-src http://archive.ubuntu.com/ubuntu xenial main restricted universe multiverse
deb http://archive.ubuntu.com/ubuntu xenial-updates main restricted universe multiverse
deb-src http://archive.ubuntu.com/ubuntu xenial-updates main restricted universe multiverse
deb http://archive.ubuntu.com/ubuntu xenial-backports main restricted universe multiverse
deb-src http://archive.ubuntu.com/ubuntu xenial-backports main restricted universe multiverse
deb http://archive.ubuntu.com/ubuntu xenial-security main restricted universe multiverse
deb-src http://archive.ubuntu.com/ubuntu xenial-security main restricted universe multiverse
#deb http://archive.ubuntu.com/ubuntu xenial-proposed restricted main universe multiverse
#deb-src http://archive.ubuntu.com/ubuntu xenial-proposed restricted main universe multiverse
deb http://archive.canonical.com/ubuntu xenial partner
deb-src http://archive.canonical.com/ubuntu xenial partner
EOF

This will overwrite your /etc/apt/sources.list file. After that you should use exit to get out of root.

If you not wish all package sources to be enabled you can change this from the GUI applet called 'Software&Updates' which you find within your settings.

Then you should do the mandatory:

sudo apt clean
sudo apt update
sudo apt dist-upgrade

This will resolve the issue

Mule SDK to Create Custom Connectors

Mule SDK to Create Custom Connectors

Create your first Mule SDK project in just a few steps:

• Install required software
• Generate a project using Maven and explore it
• Set up your IDE
• Build the project you generated
• Develop a connector or module
• Run the connector or module in Anypoint Studio

The SDK provides a Maven plugin and a Maven archetype to create new projects. The archetype is a project template; use it to ensure your new project has a consistent structure, employs recommended practices, and contains a few elements for you to experiment with.

Install the Required Software

Install and verify that the following tools are working in your local environment:

• Java Development Kit 8 (JDK 8) to compile and build your Java code.
• Apache Maven, version 3.3.9 or higher, to manage your project’s build.

Generate a Project Using the Maven Plugin

Run the generate command to create an extension project based on the Maven archetype:

mvn org.mule.extensions:mule-extensions-archetype-maven-plugin:1.2.0:generate

You are prompted to provide required field values, then a new project is generated.

The pom.xml has the following structure:

<parent> <groupId>org.mule.extensions</groupId> <artifactId>mule-modules-parent</artifactId> <version>1.1.3</version> </parent> 

 Once the code is modified to achieve the objective of the Connector, please install the connector in the repository

mvn install:install-file -DgroupId=com.mindtelligent.connect -DartifactId=MindTelligentPayloadProcessorForMule -Dversion=2.1.2 -Dclassifier=mule-plugin -Dpackaging=jar -Dfile=MindTelligentPayloadProcessorForMule-2.1.2-mule-plugin.jar

Replace the JAR file with the name of your JAR file.

 

Once your connector is working, you can try it in Anypoint Studio.

Go to your Mule app pom.xml file and add the connector as a <dependency> with its groupId, artifactId, and version.

Example: Dependency

 

 ... <dependencies> ... <dependency> <groupId>com.mindtelligent.connect</groupId> <artifactId>MindTelligentPayloadProcessorForMule </artifactId> <version>2.1.2</version> <classifier>mule-plugin</classifier> </dependency> ... </dependencies> ...

You are Ready to use the Connector

Oracle Cloud-Containerized development with Docker (Part 2)

Oracle Cloud-Containerized development with Docker (Part 2)

To tread further on this thread, you must have done the following:

• Create a compartment
• Create a Virtual Cloud Network. 

Please refer to Part 1 of this thread

Add a Security List
  
A security list provides a virtual firewall for an instance, with ingress and egress rules that specify the types of traffic allowed in and out. Each security list is enforced at the instance level. However, you configure your security lists at the subnet level, which means that all instances in a given subnet are subject to the same set of rules. The security lists apply to a given instance whether it's talking with another instance in the VCN or a host outside the VCN.

• In the DockerVCN network click on Security Lists

 

•  Click on Default Security List for DockerVCN

 

•  Click Add Ingress Rule

•  In the Pop up dialog Enter the following and then click the Add Ingress Rule button.

 

• When completed your Ingress Rules should look like:

• 

Oracle Cloud-Containerized development with Docker

Oracle Cloud-Containerized development with Docker (Part 1)
This post elucidates the deployment of Docker on Oracle Cloud.

Once the Oracle Cloud Account is fully provisioned, sign into Oracle account.

Sign into Oracle Cloud

• From any browser go to oracle.com to access Oracle Cloud.
•  https://www.oracle.com/
• Click the icon in the upper right corner. Click on Sign in to Cloud at the bottom of the drop down.    
•  Enter your Cloud Account Name in the input field and click the My Services button. If you have a Free Tier account provisioned, this can be found in your welcome email. Otherwise, this will be supplied by your workshop instructor.

• Enter your Cloud Account Name in the input field and click the My Services button.
• Enter your Username and Password in the input fields and click Sign In

Create a Compartment:

Compartments are used to isolate resources within your OCI tenant. User-based access policies can be applied to manage access to compute instances and other resources within a Compartment.

•  Click the hamburger icon in the upper left corner to open the navigation menu. Under the Identity section of the menu, click Compartments
• Click Create Compartment

• In the Name field, enter any name you want. For this example we will be using the name Demo going forward. Enter a Description of your choice. Click Create Compartment.

After the compartment is created successfully, it will display a list:




Create a VCN (Virtual Cloud Network):

• Click the hamburger icon in the upper left corner to open the navigation menu. Under the Networking section of the menu, click Virtual Cloud Networks

•  Select your compartment from the List Scope dropdown menu. 
• Click Networking Quickstart.
• Select VCN with Internet Connectivity. 
• Click Networking Quickstart.
• Select VCN with Internet Connectivity, then click Start Workflow

• Fill in the following values as highlighted below:

 

• Click Next, then Create.
• Click View Virtual Cloud Network. You will see: