Board
Alberto Tono
Hannah Tono
Elena Colombini
Tang Li Qun
Joseph Leybovich
Main Page
First Name
Last Name
Years in Office
Alberto
Tono
2020
Hannah
Tono
2020
Elena
Colombini
2020
Tang Li
Qun
2020
Joseph
Leybovich
2020
Alberto Tono
Core Values:
Sharing
Trust
Transparency
Efficiency
Sharing
Trust
Person 2
Core Values:
Person 3
Complete the Form below to join the "COMMIT BACK" journey program
Apply


If you're new to Mesos
See the getting started page for more information about downloading, building, and deploying Mesos.
If you'd like to get involved or you're looking for support
See our community page for more details.
Port Mapping Network Isolator
The port mapping network isolator provides a way to achieve per-container network monitoring and isolation without relying on IP per container. The network isolator prevents a single container from exhausting the available network ports, consuming an unfair share of the network bandwidth or significantly delaying packet transmission for others. Network statistics for each active container are published through the /monitor/statistics endpoint on the agent. The port mapping network isolator is transparent for the majority of tasks running on an agent (those that bind to port 0 and let the kernel allocate their port).
Installation
Port mapping network isolator is not supported by default. To enable it you need to install additional dependencies and configure it during the build process.
Prerequisites
Per-container network monitoring and isolation is only supported on Linux kernel versions 3.6 and above. Additionally, the kernel must include these patches (merged in kernel version 3.15).
- 6a662719c9868b3d6c7d26b3a085f0cd3cc15e64
- 0d5edc68739f1c1e0519acbea1d3f0c1882a15d7
- e374c618b1465f0292047a9f4c244bd71ab5f1f0
- 25f929fbff0d1bcebf2e92656d33025cd330cbf8
The following packages are required on the agent:
Additionally, if you are building from source, you need will also need the libnl3 development package to compile Mesos:
- libnl3-devel / libnl3-dev >= 3.2.26
Build
To build Mesos with port mapping network isolator support, you need to add a configure option:
$ ./configure --with-network-isolator
$ make
Configuration
The port mapping network isolator is enabled on the agent by adding
network/port_mapping
to the agent command line --isolation
flag.
--isolation="network/port_mapping"
If the agent has not been compiled with port mapping network isolator support, it will refuse to start and print an error:
I0708 00:17:08.080271 44267 containerizer.cpp:111] Using isolation: network/port_mapping
Failed to create a containerizer: Could not create MesosContainerizer: Unknown or unsupported
isolator: network/port_mapping
Configuring network ports
Without port mapping network isolator, all the containers on a host share the public IP address of the agent and can bind to any port allowed by the OS.
When the port mapping network isolator is enabled, each container on the agent has a separate network stack (via Linux network namespaces). All containers still share the same public IP of the agent (so that the service discovery mechanism does not need to be changed). The agent assigns each container a non-overlapping range of the ports and only packets to/from these assigned port ranges will be delivered. Applications requesting the kernel assign a port (by binding to port 0) will be given ports from the container assigned range. Applications can bind to ports outside the container assigned ranges but packets from to/from these ports will be silently dropped by the host.
Mesos provides two ranges of ports to containers:
OS allocated “ephemeral” ports are assigned by the OS in a range specified for each container by Mesos.
Mesos allocated “non-ephemeral” ports are acquired by a framework using the same Mesos resource offer mechanism used for cpu, memory etc. for allocation to executors/tasks as required.
Additionally, the host itself will require ephemeral ports for network communication. You need to configure these three non-overlapping port ranges on the host.
Host ephemeral port range
The currently configured host ephemeral port range can be discovered at any time
using the command sysctl net.ipv4.ip_local_port_range
. If ports need to be set
aside for agent containers, the ephemeral port range can be updated in
/etc/sysctl.conf
. Rebooting after the update will apply the change and
eliminate the possibility that ports are already in use by other processes. For
example, by adding the following:
# net.ipv4.ip_local_port_range defines the host ephemeral port range, by
# default 32768-61000. We reduce this range to allow the Mesos agent to
# allocate ports 32768-57344
# net.ipv4.ip_local_port_range = 32768 61000
net.ipv4.ip_local_port_range = 57345 61000
Container port ranges
The container ephemeral and non-ephemeral port ranges are configured using the
agent --resources
flag. The non-ephemeral port range is provided to the
master, which will then offer it to frameworks for allocation.
The ephemeral port range is sub-divided by the agent, giving
ephemeral_ports_per_container
(default 1024) to each container. The maximum
number of containers on the agent will therefore be limited to approximately:
number of ephemeral_ports / ephemeral_ports_per_container
The master --max_executors_per_agent
flag is be used to prevent allocation of
more executors on an agent when the ephemeral port range has been exhausted.
It is recommended (but not required) that ephemeral_ports_per_container
be set
to a power of 2 (e.g., 512, 1024) and the lower bound of the ephemeral port
range be a multiple of ephemeral_ports_per_container
to minimize CPU overhead
in packet processing. For example:
--resources=ports:[31000-32000];ephemeral_ports:[32768-57344] \
--ephemeral_ports_per_container=512
Rate limiting container traffic
Outbound traffic from a container to the network can be rate limited to prevent
a single container from consuming all available network resources with
detrimental effects to the other containers on the host. The
--egress_rate_limit_per_container
flag specifies that each container launched
on the host be limited to the specified bandwidth (in bytes per second).
Network traffic which would cause this limit to be exceeded is delayed for later
transmission. The TCP protocol will adjust to the increased latency and reduce
the transmission rate ensuring no packets need be dropped.
--egress_rate_limit_per_container=100MB
We do not rate limit inbound traffic since we can only modify the network flows after they have been received by the host and any congestion has already occurred.
Egress traffic isolation
Delaying network data for later transmission can increase latency and jitter
(variability) for all traffic on the interface. Mesos can reduce the impact on
other containers on the same host by using flow classification and isolation
using the containers port ranges to maintain unique flows for each container and
sending traffic from these flows fairly (using the
FQ_Codel
algorithm). Use the --egress_unique_flow_per_container
flag to enable.
--egress_unique_flow_per_container
Putting it all together
A complete agent command line enabling port mapping network isolator, reserving ports 57345-61000 for host ephemeral ports, 32768-57344 for container ephemeral ports, 31000-32000 for non-ephemeral ports allocated by the framework, limiting container transmit bandwidth to 300 Mbits/second (37.5MBytes) with unique flows enabled would thus be:
mesos-agent \
--isolation=network/port_mapping \
--resources=ports:[31000-32000];ephemeral_ports:[32768-57344] \
--ephemeral_ports_per_container=1024 \
--egress_rate_limit_per_container=37500KB \
--egress_unique_flow_per_container
Monitoring container network statistics
Mesos exposes statistics from the Linux network stack for each container network on the /monitor/statistics agent endpoint.
From the network interface inside the container, we report the following
counters (since container creation) under the statistics
key:
| Metric | Description | Type |
|---|---|---|
net_rx_bytes |
Received bytes | Counter |
net_rx_dropped |
Packets dropped on receive | Counter |
net_rx_errors |
Errors reported on receive | Counter |
net_rx_packets |
Packets received | Counter |
net_tx_bytes |
Sent bytes | Counter |
net_tx_dropped |
Packets dropped on send | Counter |
net_tx_errors |
Errors reported on send | Counter |
net_tx_packets |
Packets sent | Counter |
Additionally, Linux Traffic Control can report the following
statistics for the elements which implement bandwidth limiting and bloat
reduction under the statistics/net_traffic_control_statistics
key. The entry
for each of these elements includes:
| Metric | Description | Type |
|---|---|---|
backlog |
Bytes queued for transmission [1] | Gauge |
bytes |
Sent bytes | Counter |
drops |
Packets dropped on send | Counter |
overlimits |
Count of times the interface was over its transmit limit when it attempted to send a packet. Since the normal action when the network is overlimit is to delay the packet, the overlimit counter can be incremented many times for each packet sent on a heavily congested interface. [2] | Counter |
packets |
Packets sent | Counter |
qlen |
Packets queued for transmission | Gauge |
ratebps |
Transmit rate in bytes/second [3] | Gauge |
ratepps |
Transmit rate in packets/second [3] | Gauge |
requeues |
Packets failed to send due to resource contention (such as kernel locking) [3] | Counter |
[1] backlog
is only reported on the bloat_reduction interface.
[2] overlimits
are only reported on the bw_limit interface.
[3] Currently always reported as 0 by the underlying Traffic Control element.
For example, these are the statistics you will get by hitting the /monitor/statistics
endpoint on an agent with network monitoring turned on:
$ curl -s http://localhost:5051/monitor/statistics | python2.6 -mjson.tool
[
{
"executor_id": "job.1436298853",
"executor_name": "Command Executor (Task: job.1436298853) (Command: sh -c 'iperf ....')",
"framework_id": "20150707-195256-1740121354-5150-29801-0000",
"source": "job.1436298853",
"statistics": {
"cpus_limit": 1.1,
"cpus_nr_periods": 16314,
"cpus_nr_throttled": 16313,
"cpus_system_time_secs": 2667.06,
"cpus_throttled_time_secs": 8036.840845388,
"cpus_user_time_secs": 123.49,
"mem_anon_bytes": 8388608,
"mem_cache_bytes": 16384,
"mem_critical_pressure_counter": 0,
"mem_file_bytes": 16384,
"mem_limit_bytes": 167772160,
"mem_low_pressure_counter": 0,
"mem_mapped_file_bytes": 0,
"mem_medium_pressure_counter": 0,
"mem_rss_bytes": 8388608,
"mem_total_bytes": 9945088,
"net_rx_bytes": 10847,
"net_rx_dropped": 0,
"net_rx_errors": 0,
"net_rx_packets": 143,
"net_traffic_control_statistics": [
{
"backlog": 0,
"bytes":<PHONE_NUMBER>52,
"drops": 77147,
"id": "bw_limit",
"overlimits": 210693719,
"packets": 107941027,
"qlen": 10236,
"ratebps": 0,
"ratepps": 0,
"requeues": 0
},
{
"backlog": 15481368,
"bytes":<PHONE_NUMBER>68,
"drops": 27081494,
"id": "bloat_reduction",
"overlimits": 0,
"packets": 107941070,
"qlen": 10239,
"ratebps": 0,
"ratepps": 0,
"requeues": 0
}
],
"net_tx_bytes":<PHONE_NUMBER>16,
"net_tx_dropped": 0,
"net_tx_errors": 0,
"net_tx_packets": 107936874,
"perf": {
"duration": 0,
"timestamp":<PHONE_NUMBER>.82807
},
"timestamp":<PHONE_NUMBER>.41595
}
}
]


[aws_escalate.py](https://github.com/RhinoSecurityLabs/Security-Research/blob/master/tools/aws-pentest-tools/aws_escalate.py) | Lists users scanned and the privesc methods they are vulnerable to
[SkyArk](https://github.com/cyberark/SkyArk) | SkyArk helps to discover, assess and secure the most privileged entities in AWS


Hallo What?
| Cuthbert Binns | History Of Magic |
| Gilderoy Lockhart | Defense Against The Dark Arts |
| Charity Burbage | Muggle Studies |
| Alastor Moody | Defense Against The Dark Arts |
| Firenze | Divination |
| Quirinus Quirrell | Defense Against The Dark Arts |
| Rubeus Hagrid | Care Of Magical Creatures |
| Horace Slughorn | Potions |
| Aurora Sinistra | Astronomy |
| Remus Lupin | Defense Against The Dark Arts |
| Severus Snape | Defense Against The Dark Arts |


Notebooks can be freely modified and re-executed through the web, offering a fully reproducible, “libre” path from data to figures.
NeuroLibre is currently at an beta stage of development. Our submission and review process are works in progress, and the production servers are not presently functioning at full capacity. Please be patient, or come back in a few months for the first stable release of the platform.


Salvatore's Portfolio
This is my portfolio.
On this site, you’ll find
My biography
My projects
My résumé


Using TrianaHelp
Introduction
TrianaHelp is a hypertext help viewer for viewing the help pages supplied with Triana applications. As the help pages
are composed using standard HTML version 3.2 TrianaHelp can also be used as a simple World Wide Web browser for viewing
both local pages and pages on the internet.
The Tools
Shown above is part of the toolbar showing the toolbar buttons together with the drop down menus above. The buttons from
left to right are
The Menus
The File Menu
From this menu you can
The Edit Menu
From this menu you can
- Copy the select text
- Select all the text
The Go Menu
From this menu you can
- Go backwards in history
- Go forwards in history
- Show the index page
- View the history
The Help Menu
From this menu you can
- Show this page
- View the about box
Open file
This shows the dialog above which allows you to view an HTML document on the local file system.
Open URL
This shows the dialog above which allows you to view an HTML document on the network. You can enter any valid URL in the
field and the help system will attempt to load that page.
History
The dialog above shows all the pages you have visited using the help system. To jump directly to a page highlight the
relevant entry and select the GO button.


Full involvement, permanent dedication, persistent pursuit for excellence.
Over the past 20 years Splendid focus on the research, production of rubber products and has always baseline adhering to 'Full participation in quality, Constantly exceed customer expectation' business philosophy. Splendid has enjoyed a great reputation in the rubber industry. Base on quality policy 'Quality is the customer, Exceeding is power', Splendid also has won the customer's trust from all over the world and will continue to innovative technology to create new value for customers.
1998
found
> 4.3
million square meters
⩽ 0.4%
ustomer return loss rate
100%
recycling and reuse of waste
76
Oil pressing machines
13
stock cutters
13
oven
8
down the flash machines
7
open mills
5
refrigerators
4
cnc
4
all inspection machines
3
internal mixers
we supply rubber parts to end user like eaton corporation, general motors, ford motor, bmw, tesla etc; provide PPAP documents/PFMEA/CONTROL PLAN/ISIR for our customers' special need; produce by customers' samples or technical drawings; make 100% inspection on our goods before shipment; have 8557+ sets molds for any customized products... Welcome to visit our factory to better understanding our production capacity.
Looking forward to the 21st century, Splendid promises that we will cultivate top talnets and produce highest quality products to meet our customer's requirements by advanced equipment. Splendid will surpass ourselves, perfect ourselves and exceed our competitors to be a shining star in the line of rubbers.


Uses of Package
org.fluentlenium.configuration
-
Classes in org.fluentlenium.configuration used by org.fluentlenium.adapter Class Description Configuration Base configuration interface that can be read and written.ConfigurationMutator Mutation interface of Configuration Properties.ConfigurationProperties FluentLenium can be configured in many ways through configuration properties.ConfigurationProperties.DriverLifecycle Driver lifecycle. -
Classes in org.fluentlenium.configuration used by org.fluentlenium.adapter.cucumber Class Description Configuration Base configuration interface that can be read and written.ConfigurationMutator Mutation interface of Configuration Properties.ConfigurationProperties FluentLenium can be configured in many ways through configuration properties.ConfigurationProperties.DriverLifecycle Driver lifecycle. -
Classes in org.fluentlenium.configuration used by org.fluentlenium.adapter.junit Class Description Configuration Base configuration interface that can be read and written.ConfigurationMutator Mutation interface of Configuration Properties.ConfigurationProperties FluentLenium can be configured in many ways through configuration properties. -
Classes in org.fluentlenium.configuration used by org.fluentlenium.adapter.junit.jupiter Class Description Configuration Base configuration interface that can be read and written.ConfigurationMutator Mutation interface of Configuration Properties.ConfigurationProperties FluentLenium can be configured in many ways through configuration properties. -
Classes in org.fluentlenium.configuration used by org.fluentlenium.adapter.sharedwebdriver Class Description Configuration Base configuration interface that can be read and written.ConfigurationProperties.DriverLifecycle Driver lifecycle. -
Classes in org.fluentlenium.configuration used by org.fluentlenium.adapter.testng Class Description Configuration Base configuration interface that can be read and written.ConfigurationMutator Mutation interface of Configuration Properties.ConfigurationProperties FluentLenium can be configured in many ways through configuration properties. -
Classes in org.fluentlenium.configuration used by org.fluentlenium.configuration Class Description AbstractFactoryRegistryImpl Abstract registry of FluentLenium factories.BaseConfiguration Base configuration class supporting setting of the global configuration.CapabilitiesFactory Factory ofCapabilities
CapabilitiesRegistry A registry ofCapabilitiesFactory
.CapabilitiesRegistryImpl Capabilities registry default implementation.Configuration Base configuration interface that can be read and written.ConfigurationFactory Creates new configuration from a container class.ConfigurationMutator Mutation interface of Configuration Properties.ConfigurationProperties FluentLenium can be configured in many ways through configuration properties.ConfigurationProperties.DriverLifecycle Driver lifecycle.ConfigurationProperties.TriggerMode Trigger mode for Screenshots and HtmlDump featuresCustomProperty Annotation configuration custom property.DefaultFactory Mark a factory as default factory that can be overriden without throwing an exception.Factory Marker interface for factories.FactoryNames Add names to a factory.FactoryPriority Defines the priority of the factory.FluentConfiguration Configure a FluentLenium test class with this annotation.FluentConfiguration.BooleanValue Boolean value used in annotation that can has a third DEFAULT value equivalent to null.IndexIgnore Classes marked with this annotation will be ignored by automatic registration inFactory
MethodInvocationReflectionFactory CapabilitiesFactory
based on invocation of a defined method.PropertiesBackend Reader interface for raw properties access.ReflectiveCapabilitiesFactory A simpleCapabilitiesFactory
that createCapabilities
instances using reflection.ReflectiveFactory Reflective factory.ReflectiveWebDriverFactory A simpleWebDriverFactory
that createWebDriver
instances using reflection.WebDriverFactory Factory ofWebDriver
, that can be registered inWebDrivers
registry.WebDrivers A registry ofWebDriverFactory
.WebDriversRegistryImpl WebDrivers registry implementation. -
Classes in org.fluentlenium.configuration used by org.fluentlenium.core Class Description Configuration Base configuration interface that can be read and written.ConfigurationFactory Creates new configuration from a container class.ConfigurationMutator Mutation interface of Configuration Properties.ConfigurationProperties FluentLenium can be configured in many ways through configuration properties.ConfigurationProperties.DriverLifecycle Driver lifecycle.ConfigurationProperties.TriggerMode Trigger mode for Screenshots and HtmlDump features -
Classes in org.fluentlenium.configuration used by org.fluentlenium.core.hook Class Description Configuration Base configuration interface that can be read and written.ConfigurationMutator Mutation interface of Configuration Properties.ConfigurationProperties FluentLenium can be configured in many ways through configuration properties. -
Classes in org.fluentlenium.configuration used by org.fluentlenium.core.hook.wait Class Description Configuration Base configuration interface that can be read and written.ConfigurationMutator Mutation interface of Configuration Properties.ConfigurationProperties FluentLenium can be configured in many ways through configuration properties. -
Classes in org.fluentlenium.configuration used by org.fluentlenium.core.inject Class Description Configuration Base configuration interface that can be read and written.ConfigurationMutator Mutation interface of Configuration Properties.ConfigurationProperties FluentLenium can be configured in many ways through configuration properties.


Pick your game:
Talking Head
Make the Raspberry Pi speak from text that you give it.
Scrolling Text
Display text on the LED matrices.
Walking Sprite
Display an animated guy walking on the LED matrices.


STRUCTURE-PROPERTY RELATIONSHIPS OF ELECTRON BEAM IRRADIATED MONOMERIC AND POLYMERIC SYSTEMS by Ha Chul Kim
Dissertation submitted to the Faculty of the Virginia Polytechnic Institute and State University in partial fulfillment of the requirements for the degree of DOCTOR OF PHILOSOPHY in
Chemical Engineering
APPROVED:
Garth L. Wilkes, Chairman
Thomas C. Ward David F. Cox 7 James P. Wigh tman tt William L. Conget 7
August, 1989
Blacksburg, Virginia


Work Experience
-
Peoplelogy Development Sdn Bhd
Dec 2016-April 2017
- - Make Calls, Identify prospect, follow up, and close sales.
- - To carry out and involve in events, workshops, or related seminar organized.
- - To plan and implement sales strategies
- - Meets and present to clients about the company's services.
-
Mersing Construction & Engineering Sdn Bhd
Jun 2016 - September 2016
- - Assist senior in day-to-day accouting task
- - Cheques preparation
- - Bank reconciliation
- - Fixed assets data entry
- - Sort and match invoices with supporting document


Update table form
Location:
Minumum Customers Per Hour:
Maximumm Customers Per Hour:
Average Cookies Per Customer:
Update table
Projected Sales by Store


This is the redesign of the place where Tradera sellers and buyers manage their transactions, payments, and shipping. This was a collaboration with two other designers to cover multiple design and product teams. I drove strategy and interaction design.
Feature coverage. The previous My Tradera had a decade’s worth of feature creep. We needed to figure out what to keep and what to cut.
Reduce complexity. The workflow, even for common tasks, is convoluted and requires digging through complex menus with many options.
Mobile first. Tradera had a huge influx of mobile users (growing 75% in two years), so we wanted to optimize for those devices.
Desktop strategy. We needed to make a decision whether to just use more screen real estate, or to develop desktop-specific functionality.
Brainstorm. Mathias and I kicked it off with an offsite design session. We then plastered our concepts all over the walls, then started grabbing people and riffing off our ideas. Later, we followed up with structured design sessions.
Engagement. Involving the entire team early helped engineering with estimation and risk assessment. The brainstorming sessions netted us some strong interaction ideas that eventually became fundamental parts of the interface.
Rapid iterative prototypes. We started with mockups in Balsamic and them moved to testing mobile clickable prototypes in Sketch and Marvel. We progressed to live betas, with the teams taking turns implementing global features.
Constant feedback. Every time we started a new feature, we asked customer support what we could do to reduce their calls. Every prototype or product release was vetted by other employees, semi-formal usability and A/B testing.
Leaner design. We stripped out a lot of features, and customers didn't miss them at all. Our new simple approach, bolstered by the 'To-Do List', does the job better than the old site ever did.
The Happy Path. We optimized the buying and selling flows to make the vast majority of transactions happen by selecting the most obvious option. Edge cases are cleaned up and revealed only in the proper context.
Mobile. The new 'To Do List' covers everyone's needs when they're on a mobile device, by sorting, prioritizing, and bubbling up the most pressing tasks right when they need them.
Desktop. Buyers don't use desktop any differently from mobile. Sellers, however, do a lot more specialized tasks, so we created more powerful sorting, filtering, and batch processing tools for that platform.
For mobile, we erred towards solving common tasks easily, and for desktop we erred towards enhancing power and productivity.
Customer delight. Our usability and A/B testing results validate our principles. People have taken to the new features, and our feedback is overwhelmingly positive.
Internal satisfaction. All Tradera employees sell and buy on the site, and we're as excited to use the new My Tradera as our customers are. We can't wait for the final release.