Next in thread → Next in month →

Re: [soa-rm] Invitation: Oasis/NGINX+ Discussion @ Wed Feb 28, 2018 9am - 9:45am (PST) ([email protected])

From
Mike Poulin <>
Date
2018-03-14T16:36:53+00:00
ID
trinity-154a82b7-88e9-4f8b-912c-484b1da5899e-1521045397989@3c-app-mailcom-lxa04
Thread
Re: [soa-rm] Invitation: Oasis/NGINX+ Discussion @ Wed Feb 28, 2018 9am - 9:45am (PST) ([email protected])
To 2): if the container is provided by a 3rd Party, i.e. neither by the OS nor by the MS owners, a clean architectural solution (considering the SO spirit) would be that the the container provider take care of the container updats caused by the OS updates - this is the work of the "copyer", not the the "origine" owner. Why so? Because OS is not a service - it is a part of the environment where the service provider - the container owner - operates and provides its 'container' service to the MS-consumer. 

 

Today, I've heard about "container orchestration". Are we once again placing a card ahead of a horse? Who set the rule 'one MS - one container'? IMO, this is not rational rule becuse requires additional (not resource) maintenence of identity of multiple containers  (images) for several MS tha need the same containers. 

 

- Michael

 

Sent: Tuesday, March 06, 2018 at 1:54 AM

From: "Ken Laskey" <>

To: "Mike Poulin" <>

Cc: 

Subject: Re: [soa-rm] Invitation: Oasis/NGINX+ Discussion @ Wed Feb 28, 2018 9am - 9:45am (PST) ()

1) VM has a full OS running on the VM.  Any supported OS can run on a VM.  A container uses the same OS as the host.  The major benefit is the image is much smaller because it makes use of the host OS and only packages what is needed besides what the OS provides.  It also takes less time to spin up a container.

 

2) The container is an image running on top of the host OS.  It is only what is needed to enable an exact duplicate of a machine running some app.  A VM could also be such an image but it is much larger because it has the full OS and takes longer to spin up.    I am assuming a consumer of an image subscribes to notifications that the image has been updated.  It is a reasonable approach but not necessarily the only one.

 

Ken

 

On Mar 4, 2018, at 2:18 PM, Mike Poulin <> wrote:

 

Hi Ken,

 

Ihave a few questions to your list:

 

1) to my knowledge, a MS container is not VM but a layer above virtualised VM. Do I have the same understanding as you?

2) what does mean a " copy of my machine" and why the one whose machine/image is copied should care of notifying the copiers; isn't this is duty of the copier to have a correct current copy? 

 

Regards,

- Michael

 

Sent: Monday, February 26, 2018 at 10:22 PM

From: "Ken Laskey" <>

To: 

Cc: , , 

Subject: [soa-rm] Re: Invitation: Oasis/NGINX+ Discussion @ Wed Feb 28, 2018 9am - 9:45am (PST) ()

Jackson,

 

I had hoped to get back to you sooner with a list of questions/interests but time has slipped away.

 

The following are possible points for discussion:

 

- how do I keep a microservices’ data store in synch with other data stores (dedicated to individual microservices or an enterprise data store)?

 

 

- when an application uses several microservices, are those microservices in the same container (VM?) or separate containers for each?
- from previous question, what are the considerations for communicating among the microservices in the same container or across containers?

 

- With microservices, I am concerned that we’ll see benefits in the short term but end up with an unwieldy set of near duplicates when there is no time invested to discover if someone else has already solved your problem, especially when their solution will be better than yours.

 

- To what extent is MS just packaging and reuse is you locally spinning up a copy of my machine image so you get to use my solution while avoiding the remote networking overhead?  The challenge is for me to notify you when I change/update my image and then you staying in synch with me to the extent that updating is necessary and provides you value.

 

I have a meeting offsite until 11:30 ET but I should be back in my office by noon.  My apologies if I am late but I expect others in the OASIS TC can keep you occupied :).

 

Looking forward to the discussion.

 

Ken

 

------------------------------------------------------------------------------
Dr. Kenneth Laskey
MITRE Corporation, M/S H330          phone: 703-983-7934
7515 Colshire Drive                           fax: 703-983-7996
McLean VA 22102-7508

 

On Feb 16, 2018, at 3:21 PM,  wrote:

 

	
		

			
			

			
more details »

			Oasis/NGINX+ Discussion

			
				
					

						
						
When

						
						
						
Wed Feb 28, 2018 9am – 9:45am Pacific Time

						
					

					

						
						
Where

						
						
						
https://nginx.zoom.us/my/keithhill (map)

						
					

					

						
						
Calendar

						
						
						


						
					

					

						
						
Who

						
						
						
							
								

									
									
•

									
									
									

									

									
   - organizer

									

									

									
								

								

									
									
•

									
									
									

									

									
 

									

									

									
								

							
						
						
					

				
			

			
My team is looking forward to speaking with you on Wednesday, February 28th to discuss your projects with Oasis. Please feel free to invite other members of your team who would benefit from the call. 

			
Agenda:

			1. Learn about your project at Oasis' environment and goals

			2. Overview of NGINX Plus and how it can be leveraged specific to your environment

			3. Q & A

			4.Next steps, schedule follow up

			
If there are any other subjects you would like to discuss, please let me know and I'll add it to the agenda. In the meantime, for any additional questions, please feel free to shoot me an email. 

			
Please use this link to access the meeting:

			https://nginx.zoom.us/my/keithhill

			(877) 853-5247

			933-707-9002

			
 

			
 

			
 

			
 

			  

			

			
Going?   Yes -  Maybe -  No more options »

			
		

		

			
			
Invitation from  Google Calendar

			
You are receiving this courtesy email at the account  because you are an attendee of this event.

			
To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar.

			
Forwarding this invitation could allow any recipient to modify your RSVP response. Learn More.

			
		

	

<invite.ics>
Next in thread → Next in month →