Re: How to partition a topic into multiple and how to create multiple Samza Containers

[mohanraj v]

Hi,

 Im trying to create more than one container in my application(Single
machine).
I have 1,00,000 records in one kafka topic.How to partition it into two and
process it in parallel. I configured my job properties as below but i didnt
get multiple containers.Kindly reply me as soon as possible to work on this
application.

machine configuration:
4GB RAM,2 cores

# Job

job.factory.class=org.apache.samza.job.yarn.YarnJobFactory
job.name=job-parser

# YARN
yarn.package.path=file:///home/hello-samza/target/hello-samza-0.10.0-dist.tar.gz
yarn.container.count=2
yarn.container.memory.mb=512
yarn.container.cpu.cores=2
#yarn.am.container.memory.mb=1024

# Task
task.class=samza.task.ParserStreamTask
task.inputs=kafka.input

# Serializers
serializers.registry.string.class=org.apache.samza.serializers.StringSerdeFactory

# Kafka System
systems.kafka.samza.factory=org.apache.samza.system.kafka.KafkaSystemFactory
systems.kafka.samza.msg.serde=string
systems.kafka.consumer.zookeeper.connect=localhost:2181/
systems.kafka.producer.bootstrap.servers=localhost:9092

# Job Coordinator
job.coordinator.system=kafka
job.coordinator.replication.factor=1



Thanks,
Mohan

Re: Review Request 44920: Remove tight coupling of Samza with Yarn. Define APIs for resource manager integration

[Chris Pettitt]

> On March 16, 2016, 8:48 p.m., Chris Pettitt wrote:
> > samza-core/src/main/java/org/apache/samza/clustermanager/SamzaAppState.java,
> >  line 36
> > 
> >
> > Agreed. This is a bit mix of atomic and mutable state. Either make it 
> > thread safe (e.g. lock down mutability of fields), ensure that remaining 
> > mutable state can be updated atomically, or decide it is not intended to be 
> > thread safe and get rid of additional locks / volatile accesses that add 
> > cost with no gain. Former is preferred :).
> 
> Jagadish Venkatraman wrote:
> Great feedback Chris! I could not agree more! :-)
> 
> SamzaAppState class is a currently a source of major problems. I did not 
> want to touch it (as it was not scoped in this refactoring). Upon digging 
> further, I realize the problem of making this thread-safe/private is slightly 
> involved.
> 
> 1. There is a jobCoordinator object that is exposed publicly as a part of 
> SamzaAppState. The jobCoordinator inturn exposes a nested jobModel instance 
> directly thorough its accessor. The JobModel embeds a LocalityManager that 
> mutates state during some public method calls. Hence, The jobModel instance 
> is *not* thread-safe and is shared concurrently across the UI threads, the 
> HTTP server threads in the queued thread pool,the SamzaAppMaster thread. 
> (Created SAMZA-899 to make the JobModel immutable)
> 
> 2. There are a bunch of state data structures that are publicly exposed 
> in SamzaAppState. These must be made thread-safe into accessors. These public 
> global variables could be mutated everywhere in Samza without regard for 
> safety/visibility or correctness. For example, there is an integer 
> containerCount that is public which is manipulated by both the metrics 
> reporter and the callback threads. (I created SAMZA-901 to track this)
> 
> I will work on both of these as these ASAP.
> 
> Jagadish Venkatraman wrote:
> Just a clarification:
> 1. The JobModel instance is shared concurrently as stated in [1]. This 
> presents a source of *potential* problems. (I believe there is not an actual 
> bug in the JobModel )
> 2. The containerCount is a public int that *could* be manipulated by both 
> the reporter and callback. I believe the current interaction does not have 
> any races (since count is just set at the startup once). But, having as 
> public non-final int *could* be a source of potential problems if it was 
> modified elsewhere.

For #2, the state of containerCount in onContainerCompleted is undefined unless 
start transitively "happens-before" onContainerCompleted. It may be that that 
holds, but it is not obvious to me (without spending more time working out the 
call graph). If it's not a problem now it could become one with a seemingly 
innocent refactoring.


- Chris


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/44920/#review123902
---


On March 16, 2016, 6:23 p.m., Jagadish Venkatraman wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/44920/
> ---
> 
> (Updated March 16, 2016, 6:23 p.m.)
> 
> 
> Review request for samza, Boris Shkolnik, Chris Pettitt, Jake Maes, Yi Pan 
> (Data Infrastructure), Navina Ramesh, and Xinyu Liu.
> 
> 
> Repository: samza
> 
> 
> Description
> ---
> 
> Samza currently has tight coupling with Yarn. This makes it impossible to 
> integrate with other resource managers like Mesos, or to run standalone 
> without any resource manager. This RB is a step to implementing SAMZA-881.
> 
> Design Doc: 
> https://issues.apache.org/jira/secure/attachment/12790540/SamzaJobCoordinatorRe-designProposal.pdf
> 
> 1.Proposed new APIs for a resource manager to integrate with Samza. 
> (SAMZA-881)
>- Defined the ContainerProcessManager abstraction, SamzaResource, 
> SamzaResourceRequest. 
>- Re-wrote the SamzaAppMaster into a ClusterBasedJobCoordinator.
>- Re-wrote yarn specific request logic by abstracting it into a 
> YarnContainerManager. 
> 2.Defined a ClusterManagerConfig to handle configurations independent of 
> Yarn/Mesos.
> 3.Made Samza's cluster interaction independent of Yarn. This separates Samza 
> specific components into samza-core and Yarn components into samza-yarn.
> 4.Readability improvements to the existing code base.
>-Added docs for most methods, member variables and classes (including on 
> thread-safety)
>- Made internal variables final to document intent, visibility across 
> threads. (trivially by adding modifiers, or by changing where they're 
> initialized.)
> 5.Refactored JobCoordinator into a JobModelReader.
> 
> TODO: Can

Review Request 45063: SAMZA-903

[Jagadish Venkatraman]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/45063/
---

Review request for samza.


Repository: samza


Description
---

As a part of the refactoring we separate out Samza specific state and Yarn 
specific state. As a result, the class SamzaAppState is moved from samza-yarn 
to samza-core.
The variables in the old SamzaAppState are now split into 
i) Refactored SamzaAppState (in samza core)
ii)YarnAppState (in samza yarn)
Hence, we will need to change the references to SamzaAppState in all the UI 
scala template classes to work with the newer refactoring. This RB creates a 
scalatev2 directory that will include the refactored templates.

This RB depends on RB:44920 

Review tools does not support a way to upload a diff against some already 
existing change-list. Hence, this RB is deceptively large.


Diffs
-

  build.gradle 16facbbf4dff378c561461786ff186bd9eed 
  
samza-core/src/main/java/org/apache/samza/clustermanager/AbstractContainerAllocator.java
 PRE-CREATION 
  
samza-core/src/main/java/org/apache/samza/clustermanager/ClusterBasedJobCoordinator.java
 PRE-CREATION 
  
samza-core/src/main/java/org/apache/samza/clustermanager/ContainerAllocator.java
 PRE-CREATION 
  
samza-core/src/main/java/org/apache/samza/clustermanager/ContainerManagerFactory.java
 PRE-CREATION 
  
samza-core/src/main/java/org/apache/samza/clustermanager/ContainerProcessManager.java
 PRE-CREATION 
  
samza-core/src/main/java/org/apache/samza/clustermanager/ContainerRequestState.java
 PRE-CREATION 
  
samza-core/src/main/java/org/apache/samza/clustermanager/HostAwareContainerAllocator.java
 PRE-CREATION 
  samza-core/src/main/java/org/apache/samza/clustermanager/ResourceFailure.java 
PRE-CREATION 
  samza-core/src/main/java/org/apache/samza/clustermanager/SamzaAppState.java 
PRE-CREATION 
  
samza-core/src/main/java/org/apache/samza/clustermanager/SamzaContainerLaunchException.java
 PRE-CREATION 
  samza-core/src/main/java/org/apache/samza/clustermanager/SamzaResource.java 
PRE-CREATION 
  
samza-core/src/main/java/org/apache/samza/clustermanager/SamzaResourceRequest.java
 PRE-CREATION 
  
samza-core/src/main/java/org/apache/samza/clustermanager/SamzaResourceStatus.java
 PRE-CREATION 
  
samza-core/src/main/java/org/apache/samza/clustermanager/SamzaTaskManager.java 
PRE-CREATION 
  samza-core/src/main/java/org/apache/samza/config/ClusterManagerConfig.java 
PRE-CREATION 
  samza-core/src/main/scala/org/apache/samza/coordinator/JobModelReader.scala 
PRE-CREATION 
  
samza-core/src/main/scala/org/apache/samza/metrics/SamzaAppMasterMetrics.scala 
PRE-CREATION 
  samza-shell/src/main/bash/run-am.sh 9545a96953baaff17ad14962e02bc12aadbb1101 
  samza-yarn/src/main/java/org/apache/samza/job/yarn/refactor/YarnAppState.java 
PRE-CREATION 
  
samza-yarn/src/main/java/org/apache/samza/job/yarn/refactor/YarnContainerManager.java
 PRE-CREATION 
  
samza-yarn/src/main/java/org/apache/samza/job/yarn/refactor/YarnContainerManagerFactory.java
 PRE-CREATION 
  
samza-yarn/src/main/java/org/apache/samza/job/yarn/refactor/YarnContainerRunner.java
 PRE-CREATION 
  samza-yarn/src/main/resources/scalatev2/WEB-INF/layouts/default.scaml 
PRE-CREATION 
  samza-yarn/src/main/resources/scalatev2/WEB-INF/views/index.scaml 
PRE-CREATION 
  samza-yarn/src/main/resources/scalatev2/css/bootstrap.min.css PRE-CREATION 
  samza-yarn/src/main/resources/scalatev2/css/font-awesome.min.css PRE-CREATION 
  samza-yarn/src/main/resources/scalatev2/css/ropa-sans.css PRE-CREATION 
  samza-yarn/src/main/resources/scalatev2/fonts/FontAwesome.otf PRE-CREATION 
  samza-yarn/src/main/resources/scalatev2/fonts/RopaSans-Regular-webfont.woff 
PRE-CREATION 
  samza-yarn/src/main/resources/scalatev2/fonts/fontawesome-webfont.eot 
PRE-CREATION 
  samza-yarn/src/main/resources/scalatev2/fonts/fontawesome-webfont.svg 
PRE-CREATION 
  samza-yarn/src/main/resources/scalatev2/fonts/fontawesome-webfont.ttf 
PRE-CREATION 
  samza-yarn/src/main/resources/scalatev2/fonts/fontawesome-webfont.woff 
PRE-CREATION 
  
samza-yarn/src/main/resources/scalatev2/fonts/glyphicons-halflings-regular.eot 
PRE-CREATION 
  
samza-yarn/src/main/resources/scalatev2/fonts/glyphicons-halflings-regular.svg 
PRE-CREATION 
  
samza-yarn/src/main/resources/scalatev2/fonts/glyphicons-halflings-regular.ttf 
PRE-CREATION 
  
samza-yarn/src/main/resources/scalatev2/fonts/glyphicons-halflings-regular.woff 
PRE-CREATION 
  samza-yarn/src/main/resources/scalatev2/img/asc.gif PRE-CREATION 
  samza-yarn/src/main/resources/scalatev2/img/bg.gif PRE-CREATION 
  samza-yarn/src/main/resources/scalatev2/img/desc.gif PRE-CREATION 
  samza-yarn/src/main/resources/scalatev2/img/samza-icon.png PRE-CREATION 
  samza-yarn/src/main/resources/scalatev2/js/bootstrap.min.js PRE-CREATION 
  samza-yarn/src/main/resources/scalatev2/js/jquery-1.11.1.min.js PRE-CREATION 
  samza-y

Re: Review Request 44405: SAMZA-882 - Detect partition count changes in input streams

[Navina Ramesh]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/44405/
---

(Updated March 19, 2016, 2:30 a.m.)


Review request for samza, Boris Shkolnik, Jake Maes, Jagadish Venkatraman, 
Xinyu Liu, and Yi Pan (Data Infrastructure).


Changes
---

Making StreamPartitionCountMonitor package private


Bugs: SAMZA-882
https://issues.apache.org/jira/browse/SAMZA-882


Repository: samza


Description
---

Adding loop.done in stream metadata cache


Adding comments in Test


Adding configuration to the docs


Fixing the swallowed exception from Scala immutable map


Updating config docs


Fixed some comments and javadoc


Diffs (updated)
-

  docs/learn/documentation/versioned/jobs/configuration-table.html 
2745a22daf3626db56da2bedad07690751a34a27 
  samza-api/src/main/java/org/apache/samza/system/ExtendedSystemAdmin.java 
PRE-CREATION 
  samza-core/src/main/scala/org/apache/samza/config/JobConfig.scala 
4f3e9a297ce2c0df0f5f25e0aad62f7bed774cd6 
  samza-core/src/main/scala/org/apache/samza/coordinator/JobCoordinator.scala 
06a96ad6ed786c22924017f894413bfa1ea34c06 
  
samza-core/src/main/scala/org/apache/samza/coordinator/StreamPartitionCountMonitor.scala
 PRE-CREATION 
  samza-core/src/main/scala/org/apache/samza/system/StreamMetadataCache.scala 
155c3d16d33d9bb9cd5410d786004c1bf2a57ed3 
  samza-core/src/main/scala/org/apache/samza/util/Util.scala 
bd0fe5fc8128c59fa6d08941ad88eed66dda622b 
  
samza-core/src/test/scala/org/apache/samza/coordinator/TestJobCoordinator.scala 
9ab1dd516871b1755ef64fa25cea47491ad781e2 
  
samza-core/src/test/scala/org/apache/samza/coordinator/TestStreamPartitionCountMonitor.scala
 PRE-CREATION 
  
samza-kafka/src/main/scala/org/apache/samza/system/kafka/KafkaSystemAdmin.scala 
9dc436a40afd7190626a8be0d716c70e0fe83c7a 
  
samza-yarn/src/test/java/org/apache/samza/job/yarn/TestContainerAllocator.java 
2b1bdab3c8de3184e930c244a8cae55813c33565 
  
samza-yarn/src/test/java/org/apache/samza/job/yarn/TestHostAwareContainerAllocator.java
 0c7a09f3e4c4c2ce6788be729d0bf4a294243c68 
  samza-yarn/src/test/java/org/apache/samza/job/yarn/TestSamzaTaskManager.java 
9da1edf6ff165ef0306de8730853ad30551a9831 

Diff: https://reviews.apache.org/r/44405/diff/


Testing
---

./gradlew clean build
Tested with a simple Samza job using hello-samza -> Verified that the metrics 
gauge is getting updated and published correctly.


Thanks,

Navina Ramesh

Send a msg to all partitions

[Louisia Famalda]

Hi,

I'm new to Samza and I'm trying to do this:
>From my standalone app, I'm writing some ActionEvents to a Kafka topic with
5 partitions

>From Samza, I want to process those events but I need to send some filters
information on how to process those events.
For example, I want to keep all messages that are coming from a specific
ZipCode.


My thinking is to have another Topic: ControlEventStream, which will be a
bootstrap kafka stream.
ControlEvent will contains a userId as the key and a list of zipCode as a
value.
My Samza task will read from those 2 topics, get the filter directives from
the ControlEventStream and then start processing all events.
A user of the system, will then be able to send a ControlEvent with a new
list of ZipCode that he wants to watch for.
* The number of users using the system is less than 10.

- Am I on the right track by using bootstrap stream + compaction to define
the list of filters that a specific user is interested in ?

Now, I need the Samza instantiated tasks to be able to receive update so a
user can Add/remove/update the list of ZipCode that he is looking for.
All ActionEvents are distributed cross all partitions and process in a
distributed way.

How do I guarantee that all Samza tasks will all receive ALL messages from
ControlEventStream, so they all have the same set of ZipCode filters.

Thanks in advance,
Louisia.

Re: How to partition a topic into multiple and how to create multiple Samza Containers

[Jagadish Venkatraman]

You can use the kafka-topics.sh tool to create a Kafka topic with your
desired umber of partitions. You can also use the tool to repartition topics

On Friday, March 18, 2016, Milinda Pathirage  wrote:

> Hi Mohan,
>
> Samza maps Kafka topic partitions to containers. So if your topic has only
> 1 partition, only 1 container will be spawned even if you configure Samza
> job to use more than 1 container. So please partition the input topic
>  first.  The "Tasks" section of [1] contains more information on this.
>
> Thanks
> Milinda
>
> [1]
>
> https://samza.apache.org/learn/documentation/0.10/introduction/concepts.html
>
> On Fri, Mar 18, 2016 at 9:11 AM, mohanraj v  > wrote:
>
> > Hi,
> >
> >  Im trying to create more than one container in my application(Single
> > machine).
> > I have 1,00,000 records in one kafka topic.How to partition it into two
> and
> > process it in parallel. I configured my job properties as below but i
> didnt
> > get multiple containers.Kindly reply me as soon as possible to work on
> this
> > application.
> >
> > machine configuration:
> > 4GB RAM,2 cores
> >
> > # Job
> >
> > job.factory.class=org.apache.samza.job.yarn.YarnJobFactory
> > job.name=job-parser
> >
> > # YARN
> >
> >
> yarn.package.path=file:///home/hello-samza/target/hello-samza-0.10.0-dist.tar.gz
> > yarn.container.count=2
> > yarn.container.memory.mb=512
> > yarn.container.cpu.cores=2
> > #yarn.am.container.memory.mb=1024
> >
> > # Task
> > task.class=samza.task.ParserStreamTask
> > task.inputs=kafka.input
> >
> > # Serializers
> >
> >
> serializers.registry.string.class=org.apache.samza.serializers.StringSerdeFactory
> >
> > # Kafka System
> >
> >
> systems.kafka.samza.factory=org.apache.samza.system.kafka.KafkaSystemFactory
> > systems.kafka.samza.msg.serde=string
> > systems.kafka.consumer.zookeeper.connect=localhost:2181/
> > systems.kafka.producer.bootstrap.servers=localhost:9092
> >
> > # Job Coordinator
> > job.coordinator.system=kafka
> > job.coordinator.replication.factor=1
> >
> >
> >
> > Thanks,
> > Mohan
> >
>
>
>
> --
> Milinda Pathirage
>
> PhD Student | Research Assistant
> School of Informatics and Computing | Data to Insight Center
> Indiana University
>
> twitter: milindalakmal
> skype: milinda.pathirage
> blog: http://milinda.pathirage.org
>


-- 
Sent from my iphone.

Re: Review Request 44405: SAMZA-882 - Detect partition count changes in input streams

[Navina Ramesh]

> On March 18, 2016, 5:07 p.m., Yi Pan (Data Infrastructure) wrote:
> > samza-core/src/main/scala/org/apache/samza/coordinator/StreamPartitionCountMonitor.scala,
> >  line 77
> > 
> >
> > Can we make sure that either a) this class is only accessible from 
> > JobCoordinator; Or b) make this class also thread-safe?
> > 
> > One concern I had here is thread safety when startMonitor() is invoked 
> > in a multi-threaded context.

I don't want to spend time on making this class thread-safe as it is most 
likely going to be part of the new JC interface and we should consider 
thread-safety more holistically. I have made it package private for now.


- Navina


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/44405/#review124223
---


On March 19, 2016, 2:30 a.m., Navina Ramesh wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/44405/
> ---
> 
> (Updated March 19, 2016, 2:30 a.m.)
> 
> 
> Review request for samza, Boris Shkolnik, Jake Maes, Jagadish Venkatraman, 
> Xinyu Liu, and Yi Pan (Data Infrastructure).
> 
> 
> Bugs: SAMZA-882
> https://issues.apache.org/jira/browse/SAMZA-882
> 
> 
> Repository: samza
> 
> 
> Description
> ---
> 
> Adding loop.done in stream metadata cache
> 
> 
> Adding comments in Test
> 
> 
> Adding configuration to the docs
> 
> 
> Fixing the swallowed exception from Scala immutable map
> 
> 
> Updating config docs
> 
> 
> Fixed some comments and javadoc
> 
> 
> Diffs
> -
> 
>   docs/learn/documentation/versioned/jobs/configuration-table.html 
> 2745a22daf3626db56da2bedad07690751a34a27 
>   samza-api/src/main/java/org/apache/samza/system/ExtendedSystemAdmin.java 
> PRE-CREATION 
>   samza-core/src/main/scala/org/apache/samza/config/JobConfig.scala 
> 4f3e9a297ce2c0df0f5f25e0aad62f7bed774cd6 
>   samza-core/src/main/scala/org/apache/samza/coordinator/JobCoordinator.scala 
> 06a96ad6ed786c22924017f894413bfa1ea34c06 
>   
> samza-core/src/main/scala/org/apache/samza/coordinator/StreamPartitionCountMonitor.scala
>  PRE-CREATION 
>   samza-core/src/main/scala/org/apache/samza/system/StreamMetadataCache.scala 
> 155c3d16d33d9bb9cd5410d786004c1bf2a57ed3 
>   samza-core/src/main/scala/org/apache/samza/util/Util.scala 
> bd0fe5fc8128c59fa6d08941ad88eed66dda622b 
>   
> samza-core/src/test/scala/org/apache/samza/coordinator/TestJobCoordinator.scala
>  9ab1dd516871b1755ef64fa25cea47491ad781e2 
>   
> samza-core/src/test/scala/org/apache/samza/coordinator/TestStreamPartitionCountMonitor.scala
>  PRE-CREATION 
>   
> samza-kafka/src/main/scala/org/apache/samza/system/kafka/KafkaSystemAdmin.scala
>  9dc436a40afd7190626a8be0d716c70e0fe83c7a 
>   
> samza-yarn/src/test/java/org/apache/samza/job/yarn/TestContainerAllocator.java
>  2b1bdab3c8de3184e930c244a8cae55813c33565 
>   
> samza-yarn/src/test/java/org/apache/samza/job/yarn/TestHostAwareContainerAllocator.java
>  0c7a09f3e4c4c2ce6788be729d0bf4a294243c68 
>   
> samza-yarn/src/test/java/org/apache/samza/job/yarn/TestSamzaTaskManager.java 
> 9da1edf6ff165ef0306de8730853ad30551a9831 
> 
> Diff: https://reviews.apache.org/r/44405/diff/
> 
> 
> Testing
> ---
> 
> ./gradlew clean build
> Tested with a simple Samza job using hello-samza -> Verified that the metrics 
> gauge is getting updated and published correctly.
> 
> 
> Thanks,
> 
> Navina Ramesh
> 
>

Re: Send a msg to all partitions

[Jagadish Venkatraman]

The incoming message envelope that you receive has methods to look up what
system or stream partition it is from. So you can choose to react
differently if this message is from a broadcast stream.

Let us know if you need more help!



On Friday, March 18, 2016, Jagadish Venkatraman 
wrote:

> Broad cast stream is the Samza feature designed for this exact
> requirement. Your thinking is on the right lines.
>
> Please take a look at task.broadcast.inputs from the Samza configuration
> reference page.
>
> On Friday, March 18, 2016, Louisia Famalda  > wrote:
>
>> Hi,
>>
>> I'm new to Samza and I'm trying to do this:
>> From my standalone app, I'm writing some ActionEvents to a Kafka topic
>> with
>> 5 partitions
>>
>> From Samza, I want to process those events but I need to send some filters
>> information on how to process those events.
>> For example, I want to keep all messages that are coming from a specific
>> ZipCode.
>>
>>
>> My thinking is to have another Topic: ControlEventStream, which will be a
>> bootstrap kafka stream.
>> ControlEvent will contains a userId as the key and a list of zipCode as a
>> value.
>> My Samza task will read from those 2 topics, get the filter directives
>> from
>> the ControlEventStream and then start processing all events.
>> A user of the system, will then be able to send a ControlEvent with a new
>> list of ZipCode that he wants to watch for.
>> * The number of users using the system is less than 10.
>>
>> - Am I on the right track by using bootstrap stream + compaction to define
>> the list of filters that a specific user is interested in ?
>>
>> Now, I need the Samza instantiated tasks to be able to receive update so a
>> user can Add/remove/update the list of ZipCode that he is looking for.
>> All ActionEvents are distributed cross all partitions and process in a
>> distributed way.
>>
>> How do I guarantee that all Samza tasks will all receive ALL messages from
>> ControlEventStream, so they all have the same set of ZipCode filters.
>>
>> Thanks in advance,
>> Louisia.
>>
>
>
> --
> Sent from my iphone.
>


-- 
Sent from my iphone.